Re: [Condor-users] rooster on linux, take 3

[Dimitri Maziuk <dmaziuk@xxxxxxxxxxxxx>]

On 11/22/2011 12:08 PM, Dan Bradley wrote:

> So for testing, if you want to wake up machines regardless of whether
> they have been matched to jobs, you could just put the following in
> rooster's configuration:
> 
> ROOSTER_UNHIBERNATE = Offline
> 
> That will attempt to unhibernate all offline machines, without reference
> to the machine's unhibernate expression.

Is that supposed to be settable with condor_config_val?

The other problem I see here is that HIBERNATE_CHECK_INTERVAL
 "... is ignored when the machine has just returned from a low power
state (excluding shutdown (5)). In order to avoid machines from
volleying between a running state and a low power state, an hour of
uptime is enforced after a machine has been woken."

Does that mean machines that hibernate to s5 are supposed to volley
between booting up and shutting down every 5 minutes? Why doesn't it
check the uptime after reboot?

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

Attachment: signature.asc
Description: OpenPGP digital signature