1just-man-pages/condor_hold(1)General Commands Manuajlust-man-pages/condor_hold(1)
2
3
4
6 condor_hold put jobs in the queue into the hold state
7
9 condor_hold [ -help -version ]
10
11 condor_hold [ -debug ] [ -pool centralmanagerhostname[:portnumber]
12 -name scheddname ][ -addr <a.b.c.d:port> ] cluster... clus‐
13 ter.process... user... -constraint expression ...
14
15 condor_hold [ -debug ] [ -pool centralmanagerhostname[:portnumber]
16 -name scheddname ][ -addr <a.b.c.d:port> ] -all
17
19 condor_hold places jobs from the Condor job queue in the hold state. If
20 the -name option is specified, the named condor_schedd is targeted for
21 processing. Otherwise, the local condor_schedd is targeted. The jobs to
22 be held are identified by one or more job identifiers, as described
23 below. For any given job, only the owner of the job or one of the queue
24 super users (defined by the QUEUE_SUPER_USERSmacro) can place the job
25 on hold.
26
27 A job in the hold state remains in the job queue, but the job will not
28 run until released with condor_release .
29
30 A currently running job that is placed in the hold state by condor_hold
31 is sent a hard kill signal. For a standard universe job, this means
32 that the job is removed from the machine without allowing a checkpoint
33 to be produced first.
34
36 -help
37
38 Display usage information
39
40
41
42 -version
43
44 Display version information
45
46
47
48 -pool centralmanagerhostname[:portnumber]
49
50 Specify a pool by giving the central manager's host name and an
51 optional port number
52
53
54
55 -name scheddname
56
57 Send the command to a machine identified by scheddname
58
59
60
61 -addr <a.b.c.d:port>
62
63 Send the command to a machine located at <a.b.c.d:port>
64
65
66
67 -debug
68
69 Causes debugging information to be sent to stderr, based on the
70 value of the configuration variable TOOL_DEBUG
71
72
73
74 cluster
75
76 Hold all jobs in the specified cluster
77
78
79
80 cluster.process
81
82 Hold the specific job in the cluster
83
84
85
86 user
87
88 Hold all jobs belonging to specified user
89
90
91
92 -constraint expression
93
94 Hold all jobs which match the job ClassAd expression constraint
95 (within quotation marks). Note that quotation marks must be escaped
96 with the backslash characters for most shells.
97
98
99
100 -all
101
102 Hold all the jobs in the queue
103
104
105
106
107
109 condor_release (on page )
110
112 To place on hold all jobs (of the user that issued the condor_hold com‐
113 mand) that are not currently running:
114
115 % condor_hold -constraint "JobStatus!=2"
116
117 Multiple options within the same command cause the union of all jobs
118 that meet either (or both) of the options to be placed in the hold
119 state. Therefore, the command
120
121 % condor_hold Mary -constraint "JobStatus!=2"
122
123 places all of Mary's queued jobs into the hold state, and the con‐
124 straint holds all queued jobs not currently running. It also sends a
125 hard kill signal to any of Mary's jobs that are currently running. Note
126 that the jobs specified by the constraint will also be Mary's jobs, if
127 it is Mary that issues this example condor_hold command.
128
130 condor_hold will exit with a status value of 0 (zero) upon success, and
131 it will exit with the value 1 (one) upon failure.
132
134 Condor Team, University of Wisconsin-Madison
135
137 Copyright (C) 1990-2009 Condor Team, Computer Sciences Department, Uni‐
138 versity of Wisconsin-Madison, Madison, WI. All Rights Reserved.
139 Licensed under the Apache License, Version 2.0.
140
141 See the Condor Version 7.4.2 Manual or http://www.condorpro‐
142 ject.org/licensefor additional notices. condor-admin@cs.wisc.edu
143
144
145
146 date just-man-pages/condor_hold(1)