condor_hold(1)

1condor_hold(1)              General Commands Manual             condor_hold(1)
2
3
4

Name

6       condor_holdput jobs in the queue into the hold state
7

Synopsis

9       condor_hold[-help | -version]
10
11       condor_hold[-debug]  [-reason  reasonstring]  [-subcode number] [ -pool
12       centralmanagerhostname[:portnumber]|   -name   scheddname]   |   [-addr
13       "<a.b.c.d:port>"]  cluster...  |  cluster.process...  | user... | -con‐
14       straint expression...
15
16       condor_hold[-debug] [-reason reasonstring] [-subcode  number]  [  -pool
17       centralmanagerhostname[:portnumber]|   -name   scheddname]   |   [-addr
18       "<a.b.c.d:port>"] -all
19

Description

21       condor_holdplaces jobs from the HTCondor job queue in the  hold  state.
22       If the -nameoption is specified, the named condor_scheddis targeted for
23       processing. Otherwise, the local condor_scheddis targeted. The jobs  to
24       be  held  are  identified  by one or more job identifiers, as described
25       below. For any given job, only the owner of the job or one of the queue
26       super  users  (defined by the QUEUE_SUPER_USERSmacro) can place the job
27       on hold.
28
29       A job in the hold state remains in the job queue, but the job will  not
30       run until released with condor_release.
31
32       A  currently  running  job  that  is  placed  in the hold state by con‐
33       dor_holdis sent a hard kill signal. For a standard universe  job,  this
34       means  that  the  job  is  removed  from the machine without allowing a
35       checkpoint to be produced first.
36

Options

38       -help
39
40          Display usage information
41
42
43
44       -version
45
46          Display version information
47
48
49
50       -pool centralmanagerhostname[:portnumber]
51
52          Specify a pool by giving the central  manager's  host  name  and  an
53          optional port number
54
55
56
57       -name scheddname
58
59          Send the command to a machine identified by scheddname
60
61
62
63       -addr <a.b.c.d:port>
64
65          Send the command to a machine located at "<a.b.c.d:port>"
66
67
68
69       -debug
70
71          Causes  debugging  information  to  be  sent to stderr, based on the
72          value of the configuration variable TOOL_DEBUG.
73
74
75
76       -reason reasonstring
77
78          Sets the job ClassAd attribute HoldReasonto the value given by  rea‐
79          sonstring.  reasonstringwill  be  delimited by double quote marks on
80          the command line, if it contains space characters.
81
82
83
84       -subcode number
85
86          Sets the job ClassAd attribute HoldReasonSubCodeto the integer value
87          given by number.
88
89
90
91       cluster
92
93          Hold all jobs in the specified cluster
94
95
96
97       cluster.process
98
99          Hold the specific job in the cluster
100
101
102
103       user
104
105          Hold all jobs belonging to specified user
106
107
108
109       -constraint expression
110
111          Hold  all  jobs  which  match  the job ClassAd expression constraint
112          (within quotation marks). Note that quotation marks must be  escaped
113          with the backslash characters for most shells.
114
115
116
117       -all
118
119          Hold all the jobs in the queue
120
121
122
123
124

Examples

129       To  place on hold all jobs (of the user that issued the condor_holdcom‐
130       mand) that are not currently running:
131
132       % condor_hold -constraint "JobStatus!=2"
133
134       Multiple options within the same command cause the union  of  all  jobs
135       that  meet  either  (or  both)  of the options to be placed in the hold
136       state. Therefore, the command
137
138       % condor_hold Mary -constraint  "JobStatus!=2"  places  all  of  Mary's
139       queued  jobs  into  the hold state, and the constraint holds all queued
140       jobs not currently running. It also sends a hard kill signal to any  of
141       Mary's jobs that are currently running. Note that the jobs specified by
142       the constraint will also be Mary's jobs, if it is Mary that issues this
143       example condor_holdcommand.
144

Exit Status

146       condor_holdwill  exit with a status value of 0 (zero) upon success, and
147       it will exit with the value 1 (one) upon failure.
148

Author

150       Center  for  High   Throughput   Computing,   University   of   Wiscon‐
151       sin&ndash;Madison
152

Copyright

154       Copyright  ©  1990-2019  Center for High Throughput Computing, Computer
155       Sciences Department, University of Wisconsin-Madison, Madison, WI.  All
156       Rights Reserved. Licensed under the Apache License, Version 2.0.
157
158
159
160                                     date                       condor_hold(1)