Re: [Condor-users] kill exprs with job props

[Derek Wright <wright@xxxxxxxxxxx>]

On Mon, 5 Dec 2005 09:48:26 -0600  Erik Paulson wrote:

> > Is KILL evaluated in the context of the running job's ClassAd?
> > 
> 
> No, it's in the machine ad.

lies, all lies.  KILL, like all startd policy expressions, is
evaluated in the context of *both* the machine ad *and* the running
job's ad.  that's why you don't have to do anything special to refer
to the job universe, imagesize, etc, in the default policy
expressions.  if you're talking about an attribute that happens to be
in both the machine and job classad, and therefore need to use classad
scoping, "MY.foo" is the "foo" attribute from the machine ad, and
"TARGET.foo" is the "foo" attribute from the currently running job.

> Export JobMaxSuspend into the machine ad with STARTD_JOB_EXPRS

that's only if you want to see the current value of JobMaxSuspend in
the machine's classad for the purposes of condor_status, etc.

enjoy,
-derek