1CONDOR_HOLD(1) HTCondor Manual CONDOR_HOLD(1)
2
6 condor_hold - HTCondor Manual
7 put jobs in the queue into the hold state
9
12 condor_hold [-help | -version ]
13 condor_hold [-debug ] [-reason reasonstring] [-subcode number] [ -pool
15 centralmanagerhostname[:portnumber] | -name scheddname ] | [-addr
16 "<a.b.c.d:port>"] cluster... | cluster.process... | user... | -con‐
17 straint expression ...
18 condor_hold [-debug ] [-reason reasonstring] [-subcode number] [ -pool
20 centralmanagerhostname[:portnumber] | -name scheddname ] | [-addr
21 "<a.b.c.d:port>"] -all
22
24 condor_hold places jobs from the HTCondor job queue in the hold state.
25 If the -name option is specified, the named condor_schedd is targeted
26 for processing. Otherwise, the local condor_schedd is targeted. The
27 jobs to be held are identified by one or more job identifiers, as de‐
28 scribed below. For any given job, only the owner of the job or one of
29 the queue super users (defined by the QUEUE_SUPER_USERS macro) can
30 place the job on hold.
31 A job in the hold state remains in the job queue, but the job will not
33 run until released with condor_release.
34 A currently running job that is placed in the hold state by condor_hold
36 is sent a hard kill signal. For a standard universe job, this means
37 that the job is removed from the machine without allowing a checkpoint
38 to be produced first.
39
41 -help Display usage information
42 -version
44 Display version information
45 -pool centralmanagerhostname[:portnumber]
47 Specify a pool by giving the central manager's host name and
48 an optional port number
49 -name scheddname
51 Send the command to a machine identified by scheddname
52 -addr "<a.b.c.d:port>"
54 Send the command to a machine located at "<a.b.c.d:port>"
55 -debug Causes debugging information to be sent to stderr, based on
57 the value of the configuration variable TOOL_DEBUG.
58 -reason reasonstring
60 Sets the job ClassAd attribute HoldReason to the value given
61 by reasonstring. reasonstring will be delimited by double
62 quote marks on the command line, if it contains space charac‐
63 ters.
64 -subcode number
66 Sets the job ClassAd attribute HoldReasonSubCode to the inte‐
67 ger value given by number.
68 cluster
70 Hold all jobs in the specified cluster
71 cluster.process
73 Hold the specific job in the cluster
74 user Hold all jobs belonging to specified user
76 -constraint expression
78 Hold all jobs which match the job ClassAd expression con‐
79 straint (within quotation marks). Note that quotation marks
80 must be escaped with the backslash characters for most
81 shells.
82 -all Hold all the jobs in the queue
84
86 condor_release
87
89 To place on hold all jobs (of the user that issued the condor_hold com‐
90 mand) that are not currently running:
91 % condor_hold -constraint "JobStatus!=2"
93 Multiple options within the same command cause the union of all jobs
95 that meet either (or both) of the options to be placed in the hold
96 state. Therefore, the command
97 % condor_hold Mary -constraint "JobStatus!=2"
99 places all of Mary's queued jobs into the hold state, and the con‐
101 straint holds all queued jobs not currently running. It also sends a
102 hard kill signal to any of Mary's jobs that are currently running. Note
103 that the jobs specified by the constraint will also be Mary's jobs, if
104 it is Mary that issues this example condor_hold command.
105
107 condor_hold will exit with a status value of 0 (zero) upon success, and
108 it will exit with the value 1 (one) upon failure.
109
111 HTCondor Team
112
114 1990-2022, Center for High Throughput Computing, Computer Sciences De‐
115 partment, University of Wisconsin-Madison, Madison, WI, US. Licensed
116 under the Apache License, Version 2.0.
1178.8 Jun 13, 2022 CONDOR_HOLD(1)