condor_release

release held jobs in the condor queue

Synopsis

condor_release [-help | -version] [-pool centralmanagerhostname | -name hostname | -addr "<a.b.c.d:port>" | hostname ...] [-master | -startd | -schedd | -collector | -negotiator | -kbdd] [cluster | cluster.process | user | -all] [-constraint constraint]

   

Description

condor_release releases one or more 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

Supported options are as follows:

-help

Display usage information

-version

Display version information

-pool centralmanagerhostname

Use the given central manager to find daemons

-name hostname

Send the specified command to specified machine

-addr "<a.b.c.d:port>"

Send the specified command to a machine's master located at "<a.b.c.d:port>"

hostname ...

A list of affected machines

-master

Send the specified command to the master (default)

-startd

Send the specified command to the startd

-schedd

Send the specified command to the schedd

-collector

Send the specified command to the collector

-kbdd

Send the specified command to the kbdd

cluster

Release all jobs in the specified cluster

cluster.process

Release the specific job in the cluster

user

Release jobs belonging to specified user

-all

Release all the jobs in the queue

-constraint constraint

Release jobs matching specified constraint

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.

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-2001 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.2.2 Manual for additional notices.