Synopsis
condor_release
[-help $|$ -version]
condor_release
[-debug]
[-pool/SPAN>centralmanagerhostname[:portnumber]
$|$ -name/SPAN>scheddname ]$|$ [-addr
"$<$a.b.c.d:port$>$"]
cluster$...$$|$ cluster.process$...$$|$ user$...$
-constraint/SPAN>expression $...$
condor_release
[-debug]
[-pool/SPAN>centralmanagerhostname[:portnumber]
$|$ -name/SPAN>scheddname ]$|$ [-addr
"$<$a.b.c.d:port$>$"]
-all
condor_release releases jobs from the Condor job queue that were previously placed in hold state. If the -name option is specified, the named condor_schedd is targeted for processing. Otherwise, the local condor_schedd is targeted. The jobs to be released are identified by one or more job identifiers, as described below. For any given job, only the owner of the job or one of the queue super users (defined by the QUEUE_SUPER_USERS macro) can release the job.
See Also
condor_hold (on page
)
% condor_release Mary
condor_release will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
See the Condor Version 7.5.6 or http://www.condorproject.org/license for additional notices.
condor-admin@cs.wisc.edu