It would seem that the processor usage settings are "backwards" from what one might normally want. The way I read it, they specify when BOINC apps can run rather that when I'd prefer them not to run. For example, I'd like BOINC apps to run full bore on the weekends and between 17:00 and 07:00 on weekdays. So I set the "every day between hours of 17:00 and 07:00" but jobs are still running. How can I set times to allow BOINC to run only between 17:00 and 07:00?

Thanks!
Bruce

I think you've set the interval correctly, but did you also set "Run based on preferences" in the Activity menu?

Gruß,
Gundolf
[edit]And did you clear the local preferences? (They override the online ones)[/edit]

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

I'm not sure those settings can actually be used to control the crunching time as desired. 17:00 to 07:00 crosses midnight into a different day. It looks as if two separate settings would be needed, one from 00:00 to 07:00, and another from 17:00 to 00:00.

I believe that the problem may be due to the later time (17:00) appearing before the earlier time (07:00). Here's my theory... (anyone from the BOINC development team, feel free to slap my knuckles if I'm wrong! :-) )...

Where the later time is specified first, BOINC interprets that to mean 'run from midnight until 17:00'. Then the earlier time appears next, which BOINC interprets to mean 'run from 07:00 until midnight'. The end result being to run continuously with no restrictions.

It almost sounds like the developers might want to consider a checkbox next to the time, allowing users to select whether to run, or suspend, during the selected hours?? That way, a user could elect to suspend between 07:00 and 17:00.

I believe that the problem may be due to the later time (17:00) appearing before the earlier time (07:00). Here's my theory... (anyone from the BOINC development team, feel free to slap my knuckles if I'm wrong! :-) )...

That's definitely not the problem! I'm not member of the development team, but I have set my (local) preferences to allow computing between 14:07 and 14:00, which effectively results in a pause from 14:00 to 14:07 (as intended).

So, again, check your Activity setting (Run based on preferences) and your local preferences. Did you set your preferences in the same venue (default, home, work, school) that the computer is attached to?

Gruß,
Gundolf

Check that BOINC is set to run based on preferences (Run always overrides the time-of-day preferences), and that the boinctray.exe tool is running. Boinctray.exe is the idle detection tool, without it the time-of-day preferences will not start on Windows 7 and Vista.

My system's set to run each day between 21:00 and 07:00, but for Sat & Sun, then it's free to race again. It's following that without trouble.

23/08/2011 21:00:00 | Cosmology@Home | Restarting task wu_082211_045138_0_0_0 using camb version 216
23/08/2011 21:00:00 | Leiden Classical | Restarting task wu_898976128_1312272503_34786_1 using classical version 556
23/08/2011 21:00:00 | Einstein@Home | Restarting task h1_0372.60_S6GC1__1870_S6BucketA_1 using einstein_S6Bucket version 101
23/08/2011 21:00:00 | surveill@home | Restarting task wu_1313621685_193295_0 using crawler version 108

..

24/08/2011 06:59:52 | Constellation | [checkpoint] result trackjack_hyend_www.hybrid-triebwerk.de_2011-08-14_00_105329_2 checkpointed
24/08/2011 06:59:57 | Constellation | [checkpoint] result trackjack_hyend_www.hybrid-triebwerk.de_2011-08-14_00_105329_2 checkpointed
24/08/2011 07:00:00 | | Suspending computation - time of day
24/08/2011 07:00:00 | Constellation | [cpu_sched] Preempting trackjack_hyend_www.hybrid-triebwerk.de_2011-08-14_00_105329_2 (removed from memory)
24/08/2011 07:00:00 | Cosmology@Home | [cpu_sched] Preempting wu_082311_010633_2_1_0 (removed from memory)
24/08/2011 07:00:00 | World Community Grid | [cpu_sched] Preempting E203017_941_C.27.C25H16N2.00744080.2.set1d06_0 (removed from memory)
24/08/2011 07:00:00 | Einstein@Home | [cpu_sched] Preempting h1_0372.60_S6GC1__1894_S6BucketA_2 (removed from memory)
24/08/2011 07:00:00 | surveill@home | [cpu_sched] Preempting wu_1313621685_230590_0 (left in memory)

---

Sorry it took me so long to say "exactly..." I had run always selected, not run based on preferences :-}

Bruce

---