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

Subsections


condor_ reschedule

Update scheduling information to the central manager

Synopsis

condor_ reschedule [-help | -version]

condor_ reschedule [-debug] [-name hostname | hostname | -addr "<a.b.c.d:port>" | "<a.b.c.d:port>" ... ]| [-all]

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

Description

condor_ reschedule updates the information about a set of machines' resources and jobs to the central manager. This command is used to force an update before viewing the current status of a machine. Viewing the status of a machine is done with the condor_ status command. condor_ reschedule also starts a new negotiation cycle between resource owners and resource providers on the central managers, so that jobs can be matched with machines right away. This can be useful in situations where the time between negotiation cycles is somewhat long, and an administrator wants to see if a job in the queue will get matched without waiting for the next negotiation cycle.

A new negotiation cycle cannot occur more frequently than every 20 seconds. Requests for new negotiation cycle within that 20 second window will be deferred until 20 seconds have passed since that last cycle.

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 hostname
Send the command to a machine identified by hostname
hostname
Send the command to a machine identified by hostname
-addr "<a.b.c.d:port>"
Send the command to a machine's master located at "<a.b.c.d:port>"
"<a.b.c.d:port>"
Send the command to a machine located at "<a.b.c.d:port>"
-all
Send the command to all machines in the pool
-debug
Causes debugging information to be sent to stderr based on the value of the configuration variable TOOL_DEBUG

Exit Status

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

Examples

To update the information on three named machines:

% condor_reschedule robin cardinal bluejay

To reschedule on a machine within a pool other than the local pool, use the -pool option. The argument is the name of the central manager for the pool. Note that one or more machines within the pool must be specified as the targets for the command. This command reschedules the single machine named cae17 within the pool of machines that has condor.cae.wisc.edu as its central manager:

% condor_reschedule -pool condor.cae.wisc.edu -name cae17

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_ restart Up: 9. Command Reference Manual Previous: condor_ release   Contents   Index
condor-admin@cs.wisc.edu