condor_ checkpoint

send a checkpoint command to jobs running on specified hosts

Synopsis

condor_ checkpoint [-help | -version]

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

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

Description

condor_ checkpoint sends a checkpoint command to a set of machines within a single pool. This causes the startd daemon on each of the specified machines to take a checkpoint of any running job that is executing under the standard universe. The job is temporarily stopped, a checkpoint is taken, and then the job continues. If no machine is specified, then the command is sent to the machine that issued the condor_ checkpoint command.

The command sent is a periodic checkpoint. The job will take a checkpoint, but then the job will immediately continue running after the checkpoint is completed. condor_ vacate, on the other hand, will result in the job exiting (vacating) after it produces a checkpoint.

If the job being checkpointed is running under the standard universe, the job produces a checkpoint and then continues running on the same machine. If the job is running under another universe, or if there is currently no Condor job running on that host, then condor_ checkpoint has no effect.

There is generally no need for the user or administrator to explicitly run condor_ checkpoint. Taking checkpoints of running Condor jobs is handled automatically following the policies stated in the configuration files.

Options

-help

Display usage information

-version

Display version information

-debug

Causes debugging information to be sent to stderr based on the value of the configuration variable TOOL_DEBUG

-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

Exit Status

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

Examples

To send a condor_ checkpoint command to two named machines:

% condor_checkpoint  robin cardinal

To send the condor_ checkpoint command to a machine within a pool of machines 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 sends the command to a the single machine named cae17 within the pool of machines that has condor.cae.wisc.edu as its central manager:

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

Author

Condor Team, University of Wisconsin-Madison

Copyright

Copyright © 1990-2006 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.3 Manual for additional notices.