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

Name

6       condor_rmremove jobs from the HTCondor queue
7

Synopsis

9       condor_rm[-help | -version]
10
11       condor_rm[-debug]  [-forcex]  [  -pool centralmanagerhostname[:portnum‐
12       ber]| -name scheddname] | [-addr "<a.b.c.d:port>"] cluster...  |  clus‐
13       ter.process... | user... | -constraint expression...
14
15       condor_rm[-debug]  [  -pool  centralmanagerhostname[:portnumber]| -name
16       scheddname] | [-addr "<a.b.c.d:port>"] -all
17

Description

19       condor_rmremoves one or more jobs from the HTCondor job queue.  If  the
20       -nameoption  is  specified, the named condor_scheddis targeted for pro‐
21       cessing. Otherwise, the local condor_scheddis targeted. The jobs to  be
22       removed  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 remove the job.
25
26       When  removing  a  grid  job, the job may remain in the &ldquo;X&rdquo;
27       state for a very long time. This is normal, as HTCondor  is  attempting
28       to communicate with the remote scheduling system, ensuring that the job
29       has been properly cleaned up. If it takes too long, or in rare  circum‐
30       stances  is never removed, the job may be forced to leave the job queue
31       by using the -forcexoption. This forcibly removes jobs that are in  the
32       &ldquo;X&rdquo;  state without attempting to finish any clean up at the
33       remote scheduler.
34

Options

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       -forcex
75
76          Force the immediate local removal of jobs in  the  'X'  state  (only
77          affects jobs already being removed)
78
79
80
81       cluster
82
83          Remove all jobs in the specified cluster
84
85
86
87       cluster.process
88
89          Remove the specific job in the cluster
90
91
92
93       user
94
95          Remove jobs belonging to specified user
96
97
98
99       -constraint expression
100
101          Remove all jobs which match the job ClassAd expression constraint
102
103
104
105       -all
106
107          Remove all the jobs in the queue
108
109
110

General Remarks

112       Use  the  -forcexargument with caution, as it will remove jobs from the
113       local queue immediately, but can orphan parts of the job that are  run‐
114       ning remotely and have not yet been stopped or removed.
115

Examples

117       For a user to remove all their jobs that are not currently running:
118
119       % condor_rm -constraint 'JobStatus =!= 2'
120

Exit Status

122       condor_rmwill exit with a status value of 0 (zero) upon success, and it
123       will exit with the value 1 (one) upon failure.
124

Author

126       Center  for  High   Throughput   Computing,   University   of   Wiscon‐
127       sin&ndash;Madison
128

130       Copyright  ©  1990-2019  Center for High Throughput Computing, Computer
131       Sciences Department, University of Wisconsin-Madison, Madison, WI.  All
132       Rights Reserved. Licensed under the Apache License, Version 2.0.
133
134
135
136                                     date                         condor_rm(1)
Impressum