next up previous contents index
Next: condor_ reschedule Up: 9. Command Reference Manual Previous: condor_ reconfig_schedd   Contents   Index

Subsections


condor_ release

release held jobs in the Condor queue

Synopsis

condor_ release [-help | -version]

condor_ release [-debug] [-pool centralmanagerhostname[:portnumber] | -name scheddname ]| [-addr "<a.b.c.d:port>"] cluster... | cluster.process... | user... | -constraint expression ...

condor_ release [-debug] [-pool centralmanagerhostname[:portnumber] | -name scheddname ]| [-addr "<a.b.c.d:port>"] -all

Description

condor_ release releases jobs from the Condor job queue that were previously placed in hold state. 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 released 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 release the job.

Options

-help
Display usage information
-version
Display version information
-pool centralmanagerhostname[:portnumber]
Specify a pool by giving the central manager's hostname and an optional port number
-name scheddname
Send the command to a machine identified by scheddname
-addr "<a.b.c.d:port>"
Send the command to a machine located at "<a.b.c.d:port>"
-debug
Causes debugging information to be sent to stderr based on the value of the configuration variable TOOL_DEBUG
cluster
Release all jobs in the specified cluster
cluster.process
Release the specific job in the cluster
user
Release jobs belonging to specified user
-constraint expression
Release all jobs which match the job ClassAd expression constraint
-all
Release all the jobs in the queue

See Also

condor_ hold (on page [*])

General Remarks

When releasing a held PVM universe job, you must release 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.) Releasing a subset of the machine classes for a PVM job is not supported.

Examples

To release all of the jobs of a user named Mary:
% condor_release Mary 

Exit Status

condor_ release will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.

Author

Condor Team, University of Wisconsin-Madison

Copyright

Copyright © 1990-2007 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. No use of the Condor Software Program is authorized without the express consent of the Condor Team. For more information contact: Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.

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 miron@cs.wisc.edu.

See the Condor Version 6.8.7 Manual for additional notices.


next up previous contents index
Next: condor_ reschedule Up: 9. Command Reference Manual Previous: condor_ reconfig_schedd   Contents   Index
condor-admin@cs.wisc.edu