Suggestions for console client - trigger actions externally
Posted: Wed Jun 11, 2008 3:41 pm
I'd like to see the console clients changed so that there is some way to affect the current running client's state.
I'm using the SMP beta console clients on a couple of quad core PCs and the regular console client on a couple more. I have had sessions fail after I exit with control-c but that seems to be the only way. I also want to either pause or have the folding stop after the current work unit completes.
Having additional command line arguments that affect the currently running client would be ideal. I'd like to see options retroactively change the oneunit, verbosity, and pause settings of the already running session while that session is still running. I'd also like a "quit" option added. If the updated option was implemented at the next checkpoint that'd be fine.
One way to do this would be to have pending instructions placed in a file that is read at each checkpoint. A harder to program but more elegent method might be implementing a remote procedure call, remoting, etc. With IPC/RPC it might be necessary to store the process id of the client running from the current directory if there isn't already some other reliable way to find it.
At least I'd like to have an alternative to control-c that could also be used in a script or batch file. For linux users it could be added to the shutdown init scripts, etc.
Just my 2 cents worth.
I'm using the SMP beta console clients on a couple of quad core PCs and the regular console client on a couple more. I have had sessions fail after I exit with control-c but that seems to be the only way. I also want to either pause or have the folding stop after the current work unit completes.
Having additional command line arguments that affect the currently running client would be ideal. I'd like to see options retroactively change the oneunit, verbosity, and pause settings of the already running session while that session is still running. I'd also like a "quit" option added. If the updated option was implemented at the next checkpoint that'd be fine.
One way to do this would be to have pending instructions placed in a file that is read at each checkpoint. A harder to program but more elegent method might be implementing a remote procedure call, remoting, etc. With IPC/RPC it might be necessary to store the process id of the client running from the current directory if there isn't already some other reliable way to find it.
At least I'd like to have an alternative to control-c that could also be used in a script or batch file. For linux users it could be added to the shutdown init scripts, etc.
Just my 2 cents worth.