Re: [Condor-users] HoldCode not implemented?

[Dan Bradley <dan@xxxxxxxxxxxx>]

Ian,

I just confirmed your findings with condor_hold not setting HoldCode.  
You will find that HoldCode is set for various internal error states 
encountered when running jobs, but in 6.7.20, it does not set it when 
the job is placed on hold via condor_hold.  We'll fix that in a future 
release.

Thanks,
--Dan

On Jul 18, 2006, at 1:03 PM, Ian Chesal wrote:

> The 6.7 docs reference a new (a very useful) HoldCode setting:
>
> http://www.cs.wisc.edu/condor/manual/v6.7/2_5Submitting_Job.html#2166
>
> But when I submit my jobs with "hold = true" the result job ad has no
> HoldCode attribute:
>
> > /opt/condor/bin/condor_q -long 43.0 | grep -i hold
> NumSystemHolds = 0
> HoldReason = "submitted on hold at user's request"
> OnExitHold = FALSE
> PeriodicHold = FALSE
>
> There's a HoldReason, but no HoldCode. If I call condor_release and 
> then
> condor_hold on the cluster there's still no HoldCode attribute. Are the
> docs ahead of the code base? I'm using 6.7.20 with the Schedd daemon
> running on RHEL3.
>
> - Ian
>
> --
> Ian R. Chesal <ichesal@xxxxxxxxxx>
> Senior Software Engineer
>
> Altera Corporation
> Toronto Technology Center
> Tel: (416) 926-8300
>
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx 
> with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at either
> https://lists.cs.wisc.edu/archive/condor-users/
> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR