Forum > GPU crunching
CPU <-> GPU rebranding
Richard Haselgrove:
Do you even need to close the Manager? I leave mine open while rebranding (if I'm interested), and just stop the daemon. Manager goes blank for a while, shows 'not connected to a client', then repopulates the tabs when boinc.exe is running again.
I think the correct restart command in this case would be
boinc --detach
to avoid getting a redundant command window (see http://boinc.berkeley.edu/wiki/Client_configuration#Command-line_options).
Marius:
--- Quote from: Richard Haselgrove on 26 Jun 2009, 09:21:22 am ---Do you even need to close the Manager? I leave mine open while rebranding (if I'm interested), and just stop the daemon. Manager goes blank for a while, shows 'not connected to a client', then repopulates the tabs when boinc.exe is running again.
I think the correct restart command in this case would be boinc --detach
--- End quote ---
I must admit i wasn't aware of that command and i had indeed trouble restarting the client, thats why i killed and restarted the manager (which in turn also starts the client).
The use of a "boinccmd --quit" and later on a "boinc -detach" does a much cleaner job then killing boincmgr and the same approach will work very niceley on win/64 (it even works for win/32 with service approach).
Thanks,
Marius
Raistmer:
Be careful with this "detach" option. It has significal delay in execution that led to trashing modified client_state or even to worse situations.
Some pause required.
Maybe better way is to kill boinc.exe process (ungraceful exit, but fast and reliable one).
Need to note that science apps can continue to work after such kill ~30 seconds. Usually they exit much faster.
Richard Haselgrove:
Surely you need the delay after the --quit ?
That's what you do before you edit client_state: how long it takes to start up again afterwards doesn't really matter? :-\
Raistmer:
I talk not about restart time, I stress that boinc --quit option doesn't stop boinc deamon immediately.
This topic was discussed already on BOINC boards. Some watchdog loop needed to see if BOINC really stopped.
For what reason BOINC devs implemented this options in such way and why they don't provide true shutdown option - covered in darkness... (as most BOINC-related questions BTW ;) )
EDIT: as experimental fact I killed BOINC's client_state completely while experimenting with rebranding script w/o "pause" in bat-file stopping BOINc....
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version