condor_ hold [-debug] [-pool centralmanagerhostname[:portnumber] | -name scheddname ]| [-addr "<a.b.c.d:port>"] cluster... | cluster.process... | user... | -constraint expression ...
condor_ hold [-debug] [-pool centralmanagerhostname[:portnumber] | -name scheddname ]| [-addr "<a.b.c.d:port>"] -all
condor_ hold places jobs from the Condor job queue in the 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 held 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 place the job on hold.
A job in the hold state remains in the job queue, but the job will not run until released with condor_ release.
A currently running job that is placed in the hold state by condor_ hold is sent a hard kill signal. For a standard universe job, this means that the job is removed from the machine without allowing a checkpoint to be produced first.
To put a PVM universe job on hold, you must put each ``process'' in the PVM job cluster on hold. (In the PVM universe, each PVM job is assigned its own cluster number, and each machine class is assigned a ``process'' number in the job's cluster.) Putting a subset of the machine classes for a PVM job on hold is not supported.
% condor_hold -constraint "JobStatus!=2"
Multiple options within the same command cause the union of all jobs that meet either (or both) of the options to be placed in the hold state. Therefore, the command
% condor_hold Mary -constraint "JobStatus!=2"places all of Mary's queued jobs into the hold state, and the constraint holds all queued jobs not currently running. It also sends a hard kill signal to any of Mary's jobs that are currently running. Note that the jobs specified by the constraint will also be Mary's jobs, if it is Mary that issues this example condor_ hold command.
condor_ hold will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
U.S. Government Rights Restrictions: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable, Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or firstname.lastname@example.org.
See the Condor Version 6.8.3 Manual for additional notices.