Is there a way to change the "Pause" value? I realize that it will pause it for a certain length, then restart. I checked my messages, and it appears it will Pause for 1 hr., then resume automatically.

Other than Suspend or limiting the time when BOINC runs, is there a way to 'pause' longer than an hour, but less than eternity?

---

You mean the Snooze? No, it's set at 1 hour. Although the developers have said, they'll look into it being user-definable in a future version (post 6.12).

---

Is there a way to change the "Pause" value? I realize that it will pause it for a certain length, then restart. I checked my messages, and it appears it will Pause for 1 hr., then resume automatically.

Other than Suspend or limiting the time when BOINC runs, is there a way to 'pause' longer than an hour, but less than eternity?

You can do it manually. For the local computer, you can write a script/batch file, which will call

boinccmd.exe --set_run_mode never [seconds]
or
boinccmd.exe --set_gpu_mode never [seconds]

See boinccmd.exe --help for details.

(You might need to set the current dir in the script to BOINC data folder, prior to starting boinccmd.)

Peter

...
(You might need to set the current dir in the script to BOINC data folder, prior to starting boinccmd.)

Peter

Surely the 'current directory' for boinccmd would be the program directory? (boinccmd - though I agree 'same directory as the client' could be worded less ambiguously).

In any event, it didn't seem to be necessary when I tried it recently.

In any event, it didn't seem to be necessary when I tried it recently.

Perhaps you have set the BOINC program directory up in the Windows path? As only then Windows will know immediately what you talk about.

Also, just to make it clear, using the boinccmd tool in a script or batch file, will not change how Snooze works. Snooze will continue to run only for 1 hour, no matter what values you set for this boinccmd voption.

---

(You might need to set the current dir in the script to BOINC data folder, prior to starting boinccmd.)

Surely the 'current directory' for boinccmd would be the program directory? (boinccmd - though I agree 'same directory as the client' could be worded less ambiguously).

In any event, it didn't seem to be necessary when I tried it recently.

(I should have written something like "BOINC-programs-path"/boinccmd.exe, my bad.) No, sorry, I've really meant the data directory, as I remember from the past (not sure which BOINC versions, on WinXP) that otherwise boinccmd was not able to authenticate. Now with recent BOINC version and Win7 it was not necessary as well. Possibly the current boinccmd already gets the path to data dir from registry? (I'm too lazy and busy to check sources for sure. The issue is also somehow mentioned in boinccmd.)

In any event, it didn't seem to be necessary when I tried it recently.

Perhaps you have set the BOINC program directory up in the Windows path? As only then Windows will know immediately what you talk about.

No, not in PATH. I've just forgot to mention the path to executable, see above.

Also, just to make it clear, using the boinccmd tool in a script or batch file, will not change how Snooze works. Snooze will continue to run only for 1 hour, no matter what values you set for this boinccmd voption.

Sure, that is true. It is just a separate icon (for batch file for pausing GPU for multiple hours), sitting in my QuickLaunch area, because I was already sick having to suspend my PrimeGrid GPU tasks for an hour multiple times daily :-)

(Thanks, Paul Chism, for "kicking me" to finally write the batch file again.)

Peter

I would like to suspend and resume boinc by executing a cmd-dos file which will be launched by the windows task scheduler. If I use the time table to organize the cpu running, the work units could be seen in the tasks manager but if click on suspend/snooze the work units are hidden.

I would like to launch 2 scripts :
- 1 to resume all work units
- 1 to suspend all work units
And I use the task scheduler to launch them when I want.


Is there another solution than doing :
boinccmd.exe --set_run_mode never [seconds]

Best regards

Wilgard

... but if click on suspend/snooze the work units are hidden.

That probably is due to your selecting only to "Show active tasks" (Tasks tab). ;-)

Is there another solution than doing :
boinccmd.exe --set_run_mode never [seconds]

I don't know any other, but why don't you want to use it? It does exactly what you want.

Gruß,
Gundolf

I would prefer to have something like : boinccmd -suspend before if I want several pause time (depends on the week day) I will have to do several script.

But as you said this command do what I want, so I will use it.

What is the selection option "Show active tasks", I don't find it (under Windows 7) ?

Thanks

What is the selection option "Show active tasks", I don't find it (under Windows 7) ?

It's a button on the Tasks tab of BOINC manager. If you have clicked it, it'll read "Show all tasks". :-)

Gruß,
Gundolf

Ok but I talked about the Windows Task Manager. In snooze/pause on a right click workdunits are not displayed.

...the work units could be seen in the tasks manager but if click on suspend/snooze the work units are hidden.

When one suspends individual tasks, or suspends BOINC, and one doesn't use "Leave applications in memory", the running applications (working on the tasks) are unloaded from memory. The tasks aren't hidden, they're just not in memory anymore.

So, if you want to leave them visible in Windows Task Manager, you have to use the "Leave applications in memory (while suspended)" preference. This uses up RAM and virtual memory, though. Depends on how much by what the applications are using.

---

Thanks Ageless,

So if I start boinc, if I don't check "Leave applications in memory" and I suspend it by executing :
boinccmd.exe --set_run_mode never [seconds]

All workunits should be suspended and not displayed ?

Thanks

Not in Windows Task Manager.
They'll still be available in BOINC Manager->Advanced view->Tasks tab, after clicking "Show all tasks".

---

Perfect thank you very much