If STARTD_NOCLAIM_SHUTDOWN is an _expression_, that _expression_ is evaluated to a number of seconds
when the Startd starts up and again on reconfig, but that _expression_ cannot reference Startd attributes. Â
So, no. That is not going to work.Â
You could do something hacky, where you had some external script watching the Startd and changing the configuration and sending a reconfig when the first job runs. In effect setting things up so that the noclaim shutdown value is 1 hour when the Startd starts
up, and is 200 seconds after the first job starts.Â
But it would probably be just as easy to have an external script handle the shutdown timing on its own.
There is an older mechanism controlled by the configuration variable DAEMON_SHUTDOWN, which is evaluated each time an update is sent to the collector.ÂÂ
you would need to set two knobs if you want to shut down both the Startd and the Master.
MASTER.DAEMON_SHUTDOWN = <_expression_>
STARTD.DAEMON_SHUTDOWN = <_expression_>
-tj
Hi all,
I am using STARTD_NOCLAIM_SHUTDOWNÂto stop machines when not used for 200 sec.
Now I have use case where I want this value to be max(uptime -1hr, 200sec) for vanilla universe.
Basically I want to keep machine up for alteast 1hr and then want to terminate if not used for 200 sec. Is there any way of doingÂthis?
Thanks and regardsÂ
Raman
_______________________________________________![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}