Questions and Answers :
Getting started :
how to terminate correctly and not receive any more WU
Message board moderation
Author | Message |
---|---|
zioriga Send message Joined: 11 Oct 00 Posts: 16 Credit: 20,065,498 RAC: 28 |
Is ther someone who knows how to to terminate correctly the actual WU and to stop receive any further WU. With Seti clasic there was the stop_after_send.txt file. And now ???? And for the other projects ??? |
joe Send message Joined: 13 Mar 03 Posts: 112 Credit: 497,631 RAC: 0 |
Set the cache size in your general preferences to 0 "Connect to network about every ... 0 days" |
canis lupus Send message Joined: 26 Oct 03 Posts: 154 Credit: 13,061 RAC: 0 |
> Set the cache size in your general preferences to 0 > > "Connect to network about every ... 0 days" > Does that work? I thought the work fetch policy was such that there would still be one WU downloaded because the CPU was "starved"... |
joe Send message Joined: 13 Mar 03 Posts: 112 Credit: 497,631 RAC: 0 |
> > Set the cache size in your general preferences to 0 > > > > "Connect to network about every ... 0 days" > > > > Does that work? I thought the work fetch policy was such that there would > still be one WU downloaded because the CPU was "starved"... I am not 100% sure what it does when the last project is empty, I used it to empty a project that I needed to detach on one PC. That worked well. If it still receives a work unit, it might help to use the CLI with the command line option -exit_when_idle |
zioriga Send message Joined: 11 Oct 00 Posts: 16 Credit: 20,065,498 RAC: 28 |
> Set the cache size in your general preferences to 0 > > "Connect to network about every ... 0 days" > This may be an idea and may be works fine !!! But I think it's not a good way to manage BOINC. I thing there should be a clear and supported action (and documented) in the BOINC menues. |
joe Send message Joined: 13 Mar 03 Posts: 112 Credit: 497,631 RAC: 0 |
> ... > But I think it's not a good way to manage BOINC. I thing there should be a > clear and supported action (and documented) in the BOINC menues. Agreed. I'm still using Seti Classic with shell scripts and batch files on several computers and even with those few options one had more influence on individual computers than with only web based settings *sigh* There will be some more influence on a single computer in 4.10, I have seen a screenshot somewhere. If I recall right, there was a way to suspend project-wise without detaching. Not sure if flush was contained, I don't think it was. |
joe Send message Joined: 13 Mar 03 Posts: 112 Credit: 497,631 RAC: 0 |
> > Set the cache size in your general preferences to 0 > > > > "Connect to network about every ... 0 days" > > > > Does that work? I thought the work fetch policy was such that there would > still be one WU downloaded because the CPU was "starved"... You're right about that, I just tried it. 0 days and it still downloaded one WU So "boinc_cli.exe -exit_when_idle" seems to be the only way (haven't tested that so far) |
Heffed Send message Joined: 19 Mar 02 Posts: 1856 Credit: 40,736 RAC: 0 |
> You're right about that, I just tried it. 0 days and it still downloaded one > WU > > So "boinc_cli.exe -exit_when_idle" seems to be the only way (haven't tested > that so far) Set your disk allocation too small to accept work... |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.