[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] feature request - vacate disabling by job
- Date: Wed, 29 Dec 2004 09:46:39 -0600
- From: Dan Bradley <dan@xxxxxxxxxxxx>
- Subject: Re: [Condor-users] feature request - vacate disabling by job
matthew hope wrote:
It strikes me that a job is better placed to indicate it's ability to
deal with a vacation event.
a submit parameter such as
JobWantVacate= true / false
could allow condor to short circuit KILL to true immediately (or
better still never send the wm_close / vacate signal and kill the job
I agree that it would be nice to have standardized job ClassAd
attributes to express the job's wishes under various circumstances.
However, you can insert your own job ClassAd attributes and reference
these in the startd policy expressions, so you don't have to wait around
for a standard set of attributes to be defined.
To insert an attribute into the job's ClassAd, simply put a "+" in front
of it in the submit file:
+JobWantVacate = False
Then you can evaluate this attribute (as an arbitrary expression) in the
WANT_VACATE = (JobWantVacate =!= False) && (...)