Questions and Answers :
Windows :
stop_after_send.txt functionality?
Message board moderation
Author | Message |
---|---|
EclipseHA Send message Joined: 28 Jul 99 Posts: 1018 Credit: 530,719 RAC: 0 |
This isn't really a windows question, but applies to all versions..... In Classic, you could create a file called "stop_after_send.txt" in the seti directory, and it would finish it's WU, and then exit. (I nice way of "finalizing" a computers work!) In BOINC, I got a system (linux) that is a P1 - 90mz! It's been crunching on the same WU for a few days (did it as a test), and it's just uploaded a second! (low water mark thing) How, in BOINC, to I specify that a host should finish what it's got queued, but ask for no new work? (a clean exit for the host, leaving no "limbo" Wu's!) If there's no way, this should be an M2 issue, as people "decomission" PC's every day, and the "clean exit" option is the nice way to do it! (-exit_when_idle on the command line doesn't seem to do anything, BTW, as the client isn't idle, and as the low water mark put a new WU in the queue some time before the current was was done!) a "-no_more_work_for_me" option seems to be needed! |
King Gorgonzola Send message Joined: 12 Jun 01 Posts: 20 Credit: 1,704 RAC: 0 |
Have u tried the "stop_after_send.txt" file? Early betas created that file now and then so .... |
EclipseHA Send message Joined: 28 Jul 99 Posts: 1018 Credit: 530,719 RAC: 0 |
> Have u tried the "stop_after_send.txt" file? Early betas created that file now > and then so .... > > Makes no difference, even with/without the command line arg. Probably planned for the "M27" version of the software.. :( |
©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.