Boinc_cmd can't suspend/resume projects

Message boards : BOINC client : Boinc_cmd can't suspend/resume projects
Message board moderation

Author	Message
Hermes Send message Joined: 5 Nov 05 Posts: 8	Message 1799 - Posted: 11 Dec 2005, 23:55:22 UTC Although the help says: --project url {reset | detach | update | suspend | resume | nomorework | allowmorework} suspend ans resume are noct implemented $ ./boinc_cmd --project http://lhcathome.cern.ch/ resume Unknown op resume $ ./boinc_cmd --project http://lhcathome.cern.ch/ suspend Unknown op suspend ID: 1799 ·
ben Send message Joined: 16 Dec 05 Posts: 4	Message 2010 - Posted: 16 Dec 2005, 18:16:39 UTC - in response to Message 1799.   i've noticed this too, and i'm very disappointed. sure would be nice to be able to do this for those of us running boinc as a background process on a unix/mac machine. can the devs give us any idea as to if suspend and resume will ever be implemented. if never, perhaps you should remove it from both the commandline help as well as the webpage docs. ID: 2010 ·
Michael Roycraft Send message Joined: 24 Nov 05 Posts: 129	Message 2015 - Posted: 16 Dec 2005, 20:46:43 UTC Hermes & ben, Just to be sure you have an actual flaw and not "pilot error", make sure that you have selected (clicked on to "highlight") an in-process workunit on the "Work" tab. If the Suspend and Resume are still greyed-out, you have an issue. Michael "The arc of history is long, but it bends toward Justice" ID: 2015 ·
Bill Michael Send message Joined: 30 Aug 05 Posts: 297	Message 2020 - Posted: 16 Dec 2005, 21:32:54 UTC - in response to Message 2015.   Just to be sure Michael, they're running the CLI version - no Manager. This is going to take a developer to answer. ID: 2020 ·
VincentV Send message Joined: 4 Jan 06 Posts: 1	Message 2395 - Posted: 4 Jan 2006, 13:52:01 UTC Had the same problem and found a way for Linux based machines. My machine does work for Seti@Home and the "setiathome_4.02_i686-pc-linux-gnu" process that does the work honours the SIGSTOP and SIGCONT signals. Don't know if that goes for other projects, though. So "kill -s SIGSTOP <proc no>" and "kill -s SIGCONT <proc no>" works as expected; is suspends and resumes the computations. ID: 2395 ·
Hermes Send message Joined: 5 Nov 05 Posts: 8	Message 2458 - Posted: 9 Jan 2006, 3:23:01 UTC - in response to Message 2395.   Had the same problem and found a way for Linux based machines. My machine does work for Seti@Home and the "setiathome_4.02_i686-pc-linux-gnu" process that does the work honours the SIGSTOP and SIGCONT signals. Don't know if that goes for other projects, though. These signals are processed by the Linux kernel; there is no way for any application to ignore them. So "kill -s SIGSTOP <proc no>" and "kill -s SIGCONT <proc no>" works as expected; is suspends and resumes the computations. But it does not start the computation for another project, while the applikation for one project is suspended. ID: 2458 ·

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.