[-graceful | -fast]
| -name hostname ]| [-addr "<a.b.c.d:port>"]
... [ | -all]
Given the (default) -graceful option, a job running under the standard universe will first produce a checkpoint and then the job will be killed. Condor will then restart the job somewhere else, using the checkpoint to continue from where it left off. A job running under the vanilla universe is killed, and Condor restarts the job from the beginning somewhere else. condor_ vacate has no effect on a machine with no Condor job currently running.
There is generally no need for the user or administrator to explicitly run condor_ vacate. Condor takes care of jobs in this way automatically following the policies given in configuration files.
condor_ vacate will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
% condor_vacate robin cardinal
To send the condor_ vacate 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_vacate -pool condor.cae.wisc.edu -name cae17
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 firstname.lastname@example.org.
See the Condor Version 6.8.3 Manual for additional notices.