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.
37
39 -help Display usage information
40 -version
42 Display version information
43 -pool centralmanagerhostname[:portnumber]
45 Specify a pool by giving the central manager's host name and
46 an optional port number
47 -name scheddname
49 Send the command to a machine identified by scheddname
50 -addr "<a.b.c.d:port>"
52 Send the command to a machine located at "<a.b.c.d:port>"
53 -debug Causes debugging information to be sent to stderr, based on
55 the value of the configuration variable TOOL_DEBUG.
56 -reason reasonstring
58 Sets the job ClassAd attribute HoldReason to the value given
59 by reasonstring. reasonstring will be delimited by double
60 quote marks on the command line, if it contains space charac‐
61 ters.
62 -subcode number
64 Sets the job ClassAd attribute HoldReasonSubCode to the inte‐
65 ger value given by number.
66 cluster
68 Hold all jobs in the specified cluster
69 cluster.process
71 Hold the specific job in the cluster
72 user Hold all jobs belonging to specified user
74 -constraint expression
76 Hold all jobs which match the job ClassAd expression con‐
77 straint (within quotation marks). Note that quotation marks
78 must be escaped with the backslash characters for most
79 shells.
80 -all Hold all the jobs in the queue
82
84 condor_release
85
87 To place on hold all jobs (of the user that issued the condor_hold com‐
88 mand) that are not currently running:
89 $ condor_hold -constraint "JobStatus!=2"
91 Multiple options within the same command cause the union of all jobs
93 that meet either (or both) of the options to be placed in the hold
94 state. Therefore, the command
95 $ condor_hold Mary -constraint "JobStatus!=2"
97 places all of Mary's queued jobs into the hold state, and the con‐
99 straint holds all queued jobs not currently running. It also sends a
100 hard kill signal to any of Mary's jobs that are currently running. Note
101 that the jobs specified by the constraint will also be Mary's jobs, if
102 it is Mary that issues this example condor_hold command.
103
105 condor_hold will exit with a status value of 0 (zero) upon success, and
106 it will exit with the value 1 (one) upon failure.
107
109 HTCondor Team
110
112 1990-2023, Center for High Throughput Computing, Computer Sciences De‐
113 partment, University of Wisconsin-Madison, Madison, WI, US. Licensed
114 under the Apache License, Version 2.0.
115 Oct 02, 2023 CONDOR_HOLD(1)