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.
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 have not yet been stopped or removed.
% condor_rm -constraint 'JobStatus =!= 2'
condor_rm will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
See the Condor Version 7.6.10 Manual or http://research.cs.wisc.edu/htcondor/ for additional notices.