[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Having Condor start in the unclaimed state
- Date: Tue, 28 Apr 2009 10:39:18 -0400
- From: Ian Chesal <ICHESAL@xxxxxxxxxx>
- Subject: Re: [Condor-users] Having Condor start in the unclaimed state
> I run condor in a Windows computer lab that by politcal policy is
> rebooted every night to install Windows updates. My question
> is about
> Condor Owner mode. Is there any way to get Condor to start in the
> unclaimed state while still keeping the same semantics as the default
> UWCS_* policy otherwise? Or..... Is there a way to change
> the node's
> state and force the unclaimed state once? This way, I could start
> Condor and then force the state if the reboot was due to the nightly
> scheduled task.
Machines always start in the Unclaimed state. They evaluate their state
against their configuration and then either stay Unclaimed (and begin to
participate in matchmaking) or move to the Owner state. Do you mean the
You can set a machine to the Owner state by setting:
START = False
You can use condor_config_val to make this a temporary setting that gets
wiped when the machine reboots:
condor_config_val -startd -rset "START = False"
Or you can make it a persistent setting and then revert to the config
file setting at your leisure:
condor_config_val -startd -set "START = False"
condor_config_val -startd -unset "START"
for more details.
This message may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, or copying of this message, or any attachments, is strictly prohibited. If you have received this message in error, please advise the sender by reply e-mail, and delete the message and any attachments. Thank you.