1just-man-pages/condor_rm(1) General Commands Manualjust-man-pages/condor_rm(1)
2
3
4
6 condor_rm remove jobs from the HTCondor queue
7
9 condor_rm [ -help -version ]
10
11 condor_rm [ -debug ] [ -forcex ] [ -pool centralmanagerhostname[:port‐
12 number] -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
19 condor_rm removes one or more jobs from the HTCondor job queue. If the
20 -name option is specified, the named condor_schedd is targeted for pro‐
21 cessing. Otherwise, the local condor_schedd is 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_USERS macro) can remove the
25 job.
26
27 When removing a grid job, the job may remain in the ``X'' state for a
28 very long time. This is normal, as HTCondor is attempting to communi‐
29 cate with the remote scheduling system, ensuring that the job has been
30 properly cleaned up. If it takes too long, or in rare circumstances is
31 never removed, the job may be forced to leave the job queue by using
32 the -forcex option. This forcibly removes jobs that are in the ``X''
33 state without attempting to finish any clean up at the remote sched‐
34 uler.
35
37 -help
38
39 Display usage information
40
41
42
43 -version
44
45 Display version information
46
47
48
49 -pool centralmanagerhostname[:portnumber]
50
51 Specify a pool by giving the central manager's host name and an
52 optional port number
53
54
55
56 -name scheddname
57
58 Send the command to a machine identified by scheddname
59
60
61
62 -addr <a.b.c.d:port>
63
64 Send the command to a machine located at <a.b.c.d:port>
65
66
67
68 -debug
69
70 Causes debugging information to be sent to stderr , based on the
71 value of the configuration variable TOOL_DEBUG .
72
73
74
75 -forcex
76
77 Force the immediate local removal of jobs in the 'X' state (only
78 affects jobs already being removed)
79
80
81
82 cluster
83
84 Remove all jobs in the specified cluster
85
86
87
88 cluster.process
89
90 Remove the specific job in the cluster
91
92
93
94 user
95
96 Remove jobs belonging to specified user
97
98
99
100 -constraint expression
101
102 Remove all jobs which match the job ClassAd expression constraint
103
104
105
106 -all
107
108 Remove all the jobs in the queue
109
110
111
113 Use the -forcex argument with caution, as it will remove jobs from the
114 local queue immediately, but can orphan parts of the job that are run‐
115 ning remotely and have not yet been stopped or removed.
116
118 For a user to remove all their jobs that are not currently running:
119
120 % condor_rm -constraint 'JobStatus =!= 2'
121
123 condor_rm will exit with a status value of 0 (zero) upon success, and
124 it will exit with the value 1 (one) upon failure.
125
127 Center for High Throughput Computing, University of Wisconsin-Madison
128
130 Copyright (C) 1990-2018 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 just-man-pages/condor_rm(1)