Forum > GPU crunching
CPU <-> GPU rebranding
Marius:
--- Quote from: Jason G on 26 Jun 2009, 02:38:01 pm ---Oh... that's the programmatic equivalent of "Yes Dear."
--- End quote ---
ROTFL, oh dear ;)
Doesn't hurt to see if boinc.exe has really closed down i guess ;D
Marius:
A new version of the rescheduler which now also works on the win/64 platform. If you are running this platform *please* make a backup copy first just in case it is not working as expected. Also there are additional settings so please check the configuration (via the tabsheets) as it needs your boinc bin and data path.
Greetings,
Marius
-Running units are now excluded from the rescheduling (better because the
slot info wasn't changed). Because of the changed deadlines it is still
possible that boinc starts other tasks while the previous running tasks
are marked as waiting.
-The platform is now also changed while rescheduling (sorry about any
inconvenience if this has caused problems)
-Because of changed locking there are two new settings for binaries and
datapath. (There is no need to copy reschedule to the datapath anymore)
-If boinc is not installed as a service it will do a "boinccmd.exe --quit"
and after the reschedule a "boinc.exe -detach". This should solve the
problems on any system where boinc is not installed as a service (win/64).
-Changed the locking scheme (it is no longer locking the stderrdae.txt to
test if boinc is running).
-Solved some problems in the test algorithm for the automatic reschedule.
[attachment deleted by admin]
Raistmer:
--- Quote from: Marius on 30 Jun 2009, 09:56:13 am ----If boinc is not installed as a service it will do a "boinccmd.exe --quit"
and after the reschedule a "boinc.exe -detach". This should solve the
problems on any system where boinc is not installed as a service (win/64).
--- End quote ---
Expect client_state.xml corruption here... (due to BOINC --quit option behavior).
Marius:
--- Quote from: Raistmer on 30 Jun 2009, 12:58:13 pm ---
--- Quote from: Marius on 30 Jun 2009, 09:56:13 am ----If boinc is not installed as a service it will do a "boinccmd.exe --quit"
and after the reschedule a "boinc.exe -detach". This should solve the
problems on any system where boinc is not installed as a service (win/64).
--- End quote ---
Expect client_state.xml corruption here... (due to BOINC --quit option behavior).
--- End quote ---
No, the command is "boinccmd.exe --quit" not "boinc.exe -quit" or are we talking about the same? Have you experienced this before and what are the circumstances that happened?
if you refer to boinc.exe not exiting immediately, i have that covered by checking if the process has exited. Has been running well for the last couple of days.
Greetings,
Marius
Raistmer:
--- Quote from: Marius on 30 Jun 2009, 01:16:05 pm ---if you refer to boinc.exe not exiting immediately, i have that covered by checking if the process has exited. Has been running well for the last couple of days.
--- End quote ---
Fine, if you do additional check all should be OK then.
Yes, I meant that boinc doesn't exit immediately and boinccmd --quit returns before boinc.exe will finish.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version