I want to stop crunching between noon and 7pm weekdays when electricity is most expensive for me.

In Boinc Manager I clicked Tools -> Computing Preferences. I filled in the boxes for Every day between hours of 19:00 and 12:00. I checked the boxes for Saturday and Sunday and entered 00:00-00:00 into their time boxes.

I clicked Advanced -> Read local prefs file. The event log shows the local prefs being read but says nothing about the schedule.

I did this after 7pm last night. I expected Seti to stop at noon today but it kept on running. I tried shutting down Boinc and restarting it. Seti still ran.

Can anyone help me get this to work?

---

The Universe is not only stranger than you imagine, it's stranger than you can imagine.

SETI@home classic workunits 1,405 CPU time 57,318 hours

Did you really tell it to not work
between 7:00pm and noon the next day?

Did you really tell it to not work
between 7:00pm and noon the next day?

The wording at the top of the preferences window is "Computing allowed" so I think I'm telling it to run between 7pm and noon. It's after 7 here now and seti is still running so that's not the problem.

There's no way to say "from midnight to noon AND 7pm to midnight"

---

The Universe is not only stranger than you imagine, it's stranger than you can imagine.

SETI@home classic workunits 1,405 CPU time 57,318 hours

Hmmmm....

My guess is there is a problem with using 00:00-00:00 as the signal to run all day for the weekend schedule, so try a time value not in the range you want it to run in during the week. 12:00-12:00 for example.

Hmmmm....

My guess is there is a problem with using 00:00-00:00 as the signal to run all day for the weekend schedule, so try a time value not in the range you want it to run in during the week. 12:00-12:00 for example.

Or the problem is with using 0:00, maybe 24:00 is required.
As suggested i'd enter times- such as a few minutes from now, when you want it to run or not to check that it does work, and give you an idea of what values you can use (0:00/24:00 usage can often cause problems- try using 0:05 and 23:55 as start/end values to avoid such abiguity).

---

Grant
Darwin NT

Could be, but I was thinking more along the lines that weekday run period start and stop times implies overlapping the next day, which would carry into Saturday.

The documentation for the dialog method used with the simple view showed 00:00 and 24:00 as both being valid values, so some experimentation might be required.

I took the 00:00-00:00 out of the Saturday and Sunday boxes and unchecked them so I only have the one time schedule. I changed 19:00 to 20:00 since it's between 7 and 8pm here. Clicked read prefs, seti's still running.

Should something about the schedule appear in the event log?

---

The Universe is not only stranger than you imagine, it's stranger than you can imagine.

SETI@home classic workunits 1,405 CPU time 57,318 hours

Do you need to shutdown then restart S@H?

I changed 19:00 to 20:00 since it's between 7 and 8pm here. Clicked read prefs, seti's still running.

No need to read preferences- as soon as you change the values & click OK, they take effect.
I just tried it & my crunching stopped dead.
In the Tasks tab they all showed "Suspended due to time of day restriction" (or something very similar).

---

Grant
Darwin NT

I can't seem to get any time of day preferences to work. I've tried local. I've tried clearing local and setting time of day on the website, then updating. Nothing I do will make Seti stop crunching. Obviously it works for others. What could I be missing?

---

The Universe is not only stranger than you imagine, it's stranger than you can imagine.

SETI@home classic workunits 1,405 CPU time 57,318 hours

I can't seem to get any time of day preferences to work. I've tried local. I've tried clearing local and setting time of day on the website, then updating. Nothing I do will make Seti stop crunching. Obviously it works for others. What could I be missing?

I'm running v6.10.58.
I click on Advanced, Preferences.
Local time here is 13:40.
I entered 09:00 and 13:00
Clicked on OK down the bottom & everything stopped dead.
I'd also double check your clock on the computer.

---

Grant
Darwin NT

I'm running 7.0.64.
I tried similar tests. No Joy.
My clock seems fine. The Boinc event log shows the correct time.

---

The Universe is not only stranger than you imagine, it's stranger than you can imagine.

SETI@home classic workunits 1,405 CPU time 57,318 hours

Hopefully somone running 7.0.64 can give it a go & see if it's a bug with that manager.

---

Grant
Darwin NT

You did set computing allowed based on prefs didn't you? From the activity menu across the top. It also allows for GPU settings and network (run always, prefs or never). Just setting the times isn't enough you also need to tell it to use them.

---

BOINC blog

In your "Activity" tab, there are 3 choices:
Run Always, Run based on Preferences, and Suspend.
If you want to set "Time of Day" restrictions, you must click "Run Based on Preferences".

edit] And MarkJ is a couple minutes faster than me.

---

Donald
Infernal Optimist / Submariner, retired

In your "Activity" tab, there are 3 choices:
Run Always, Run based on Preferences, and Suspend.
If you want to set "Time of Day" restrictions, you must click "Run Based on Preferences".

Ah, that makes sense.
Always had mine set to "Run based on preferences".

---

Grant
Darwin NT

Thanks, that was the problem. I knew somebody would figure it out. Now I'll set it back to 19:00-12:00 and see if it stops tomorrow at noon. If that works I'll set the overrides for Saturday and Sunday.

Thanks again to everyone who helped.

---

The Universe is not only stranger than you imagine, it's stranger than you can imagine.

SETI@home classic workunits 1,405 CPU time 57,318 hours