condor_ rm [-debug] [-forcex] [-pool centralmanagerhostname[:portnumber] | -name scheddname ]| [-addr "<a.b.c.d:port>"] cluster... | cluster.process... | user... | -constraint expression ...
condor_ rm [-debug] [-pool centralmanagerhostname[:portnumber] | -name scheddname ]| [-addr "<a.b.c.d:port>"] -all
condor_ rm removes one or more jobs from the Condor job queue. If the -name option is specified, the named condor_ schedd is targeted for processing. Otherwise, the local condor_ schedd is targeted. The jobs to be removed are identified by one or more job identifiers, as described below. For any given job, only the owner of the job or one of the queue super users (defined by the QUEUE_SUPER_USERS macro) can remove the job.
When removing a grid job, the job may remain in the ``X'' state for a very long time. This is normal, as Condor is attempting to communicate with the remote scheduling system, ensuring that the job has been properly cleaned up. If it takes too long, or in rare circumstances is never removed, the job may be forced to leave the job queue by using the -forcex option. This forcibly removes jobs that are in the ``X'' state without attempting to finish any clean up at the remote scheduler.
When removing a PVM universe job, you should always remove the entire job cluster. (In the PVM universe, each PVM job is assigned its own cluster number, and each machine class is assigned a ``process'' number in the job's cluster.) Removing a subset of the machine classes for a PVM job is not supported.
Use the -forcex argument with caution, as it will remove jobs from the local queue immediately, but can ``orphan'' parts of the job that are running remotely and haven't yet been stopped or removed.
% condor_rm Mary -constraint Activity!=\"Busy\"Note that quotation marks must be escaped with the backslash characters for most shells.
condor_ rm will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
U.S. Government Rights Restrictions: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable, Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or email@example.com.
See the Condor Version 6.8.3 Manual for additional notices.