1CONDOR_RM(1)                    HTCondor Manual                   CONDOR_RM(1)
2
3
4

NAME

6       condor_rm - HTCondor Manual
7
8       remove jobs from the HTCondor queue
9
10

SYNOPSIS

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

DESCRIPTION

22       condor_rm removes one or more jobs from the HTCondor job queue. If  the
23       -name option is specified, the named condor_schedd is targeted for pro‐
24       cessing. Otherwise, the local condor_schedd is targeted. The jobs to be
25       removed are identified by one or more job identifiers, as described be‐
26       low. For any given job, only the owner of the job or one of  the  queue
27       super  users  (defined  by  the QUEUE_SUPER_USERS macro) can remove the
28       job.
29
30       When removing a grid job, the job may remain in the  "X"  state  for  a
31       very  long  time. This is normal, as HTCondor is attempting to communi‐
32       cate with the remote scheduling system, ensuring that the job has  been
33       properly  cleaned up. If it takes too long, or in rare circumstances is
34       never removed, the job may be forced to leave the job  queue  by  using
35       the  -forcex  option.  This  forcibly  removes jobs that are in the "X"
36       state without attempting to finish any clean up at  the  remote  sched‐
37       uler.
38

OPTIONS

40          -help  Display usage information
41
42          -version
43                 Display version information
44
45          -pool centralmanagerhostname[:portnumber]
46                 Specify  a pool by giving the central manager's host name and
47                 an optional port number
48
49          -name scheddname
50                 Send the command to a machine identified by scheddname
51
52          -addr "<a.b.c.d:port>"
53                 Send the command to a machine located at "<a.b.c.d:port>"
54
55          -debug Causes debugging information to be sent to stderr,  based  on
56                 the value of the configuration variable TOOL_DEBUG.
57
58          -forcex
59                 Force  the  immediate  local removal of jobs in the 'X' state
60                 (only affects jobs already being removed)
61
62          cluster
63                 Remove all jobs in the specified cluster
64
65          cluster.process
66                 Remove the specific job in the cluster
67
68          user   Remove jobs belonging to specified user
69
70          -constraint expression
71                 Remove all jobs which match the job ClassAd  expression  con‐
72                 straint
73
74          -all   Remove all the jobs in the queue
75

GENERAL REMARKS

77       Use  the -forcex argument with caution, as it will remove jobs from the
78       local queue immediately, but can orphan parts of the job that are  run‐
79       ning remotely and have not yet been stopped or removed.
80

EXAMPLES

82       For a user to remove all their jobs that are not currently running:
83
84          % condor_rm -constraint 'JobStatus =!= 2'
85

EXIT STATUS

87       condor_rm  will  exit with a status value of 0 (zero) upon success, and
88       it will exit with the value 1 (one) upon failure.
89

AUTHOR

91       HTCondor Team
92

94       1990-2022, Center for High Throughput Computing, Computer Sciences  De‐
95       partment,  University  of  Wisconsin-Madison, Madison, WI, US. Licensed
96       under the Apache License, Version 2.0.
97
98
99
100
1018.8                              Jun 13, 2022                     CONDOR_RM(1)
Impressum