Logical shutdown
3 Apr 2005 22:58:30 UTC
Topic 188859
(moderation:
I have installed BOINC on several systems, and I noticed that there is no way with the windows version, or the newest linux version, to let the system complete it's tasks and not get immediatley re-tasked. I am going to be moving and have at least part of my systems down for at least 2 weeks. It makes more sense to allow a system to complete it's tasks and not get re-tasked than to be tasked and then be moved (as in my case), or in the case of maintence the drive formatted and the data lost and re-shipped to another system.
Logical shutdown
)
It is being worked on. Appearently BOINCveiw already has the funtionallity to do this. Sorry I don't have the URL for it though.
BOINC WIKI
BOINCing since 2002/12/8
> [...] there is no way >
)
> [...] there is no way
> with the windows version, or the newest linux version, to let the system
> complete it's tasks and not get immediatley re-tasked.
One workaround might be to cut down on the disk space you allow to BOINC, which should prevent further work being assigned. Hopefully this would not prevent completion of existing work.
If you have more than one machine, and only want to run down one of them, define a separate set of preferences for (say) 'school' to use for the graceful rundown of a machine, leaving the other machines on (say) 'home'.
~~gravywavy
BOINCVIEW Website
)
BOINCVIEW Website http://boincview.amanheis.de/
Link to Unofficial Wiki for BOINC, by Paul and Friends
I'll try that and see if it
)
I'll try that and see if it works. I almost have my doubts about cutting the disk space, because unless I cut it to basicly zero won't i just get smaller and smaller packages?
It worked, here are the
)
It worked, here are the settings required to 'starve the project'.
Disk Settings:
Use no more than .00001 GB disk space
Leave at least 99 GB disk space free
Use no more than .001% of total disk space
Write to disk at most every 60 seconds
Use no more than .001% of total virtual memory
It eventually starved a smaller SETI fed system, so my guess is, that it will work for all projects
other than a refresh of the project to clear the last status bar, there was no problem.
Thank you
> It worked, here are the
)
> It worked, here are the settings required to 'starve the project'.
> Disk Settings:
> Use no more than .00001 GB disk space
> Leave at least 99 GB disk space free
> Use no more than .001% of total disk space
> Write to disk at most every 60 seconds
> Use no more than .001% of total virtual memory
> It eventually starved a smaller SETI fed system, so my guess is, that it will
> work for all projects
>
> other than a refresh of the project to clear the last status bar, there was no
> problem.
>
> Thank you
>
>
when you say 'refresh' do you mean 'reset' or 'update'?
There is an important difference. Update will save your final WU, Reset probably will not. Either way you clear the list of WU held, but update is the only one that is a truly clean finish.
After update wait for the WU to go away and only then you can detach (if you are through with E@H)
~~gravywavy
update
)
update
I just saw that BOINC is
)
I just saw that BOINC is going to have the capability installed in the future
actually it is in the code now ( ### .25) but there isn't a user interface yet to use it
refer to this thread:
http://einsteinathome.org/node/188865
it also mentions a plug-in that does it (plug-in code is what has been added to boinc.25 from what I gather... refer to thread for all facts)
==========================================
a Chicago user who likes to be usefull