Re: [condor-users] requiring a project code to start a job

[David Kotz <dkotz@xxxxxxxxxxxxx>]

Thanks very much.

- dave


On Thu, 2004-07-08 at 03:06, Derek Wright wrote:

> 
> (...) && $(ValidProject) && (TARGET.ProjectDescription =!= UNDEFINED)
> 
> given this, if ProjectDescription isn't in a job ClassAd, you'll get
> 
> (...) && (UNDEFINED =!= UNDEFINED)
> 
> and since UNDEFINED *is* UNDEFINED, this clause will become FALSE, and
> the whole thing will be FALSE.
> 
> if there's a value, you'd get something like this:
> 
> (...) && ("doing real work" =!= UNDEFINED)
> 
> since the string "doing real work" is not UNDEFINED, this clause
> remains TRUE and the rest of the expression can do its magic...  
> 
> hope that all makes sense.
> 
> > The second problem with the above scenario is that the startd exits
> > after complaining about a syntax error in evaluating the !UWCS_START
> > expression.
> 
> that's what jamie was talking about. ;)
> 
> good luck,
> 
> -derek
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> http://lists.cs.wisc.edu/mailman/listinfo/condor-users