Is there a way to tell a client to complete and report the current WU(s) and not request a new one?
My machines are powered by solar and a battery, as well as being located somewhere where on an exceptionally hot day they can start to thermally throttle, so it'd be great to be able to put a hook into some code which requests the weather for the next day and shuts down some of them overnight once they've completed and reported their current work unit.
At the moment I'm blocking the fetching of new work units by putting the following into the hosts file;
You can use the Finish command which will instruct the client to finish folding the current WU and then not request any. Also, if you would like to fold X WUs and then pause the system, you can use this setting:
At least one folder has recently written code to use the finish flag to ensure their kit isn't folding when they want it for work … They have it start after work hours and run a finish command a couple of hours before.
It should therefore be possible for you to code something that looks at your local weather forecast on the web and uses that to trigger a finish command if the weather is forecast to be too warm … but a simpler one would just be a script you set going in the evening if the forecast for the next day is "hot" that sends a finish command to the client at an appropriate time … What that time will be will be a judgement call on your part as it may depend on WU size and how quick your kit is.
If you search around the forums a bit you should find the topic from the folder who did this recently if you need advice … Will also depend a lot on what OS you are running as to how this might be best approached.
I'd highly appreciate a possibilty of telling the client "Finish and Shutdown Windows".
I am also running on PV-Energy and would really like to let a job finish, submit and subsequently switch off my computer. A simple thing of environmental responsibility and money saving.
As mentioned, the client can be controlled through scripts. The client is accessible through the telnet protocol on port 36330 connecting to the local IP 127.0.0.1. You can connect directly using telnet or netcat to that address and port.
Or you can send commands using FAHClient --send as mentioned in the linked topic. Documentation is provided by FAHClient --help.