condor_vacate causes HTCondor to checkpoint any running jobs
on a set of machines
and force the jobs to vacate the machine.
The job(s) remains in
the submitting machine's job queue.

Given the (default) -graceful option,
a job running under the standard universe
will first produce a checkpoint and then the job will be killed.
HTCondor 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 HTCondor
restarts the job from the beginning somewhere else.
condor_vacate has no effect on a machine with
no HTCondor job currently running.

There is generally no need for the user or administrator to explicitly run
condor_vacate.
HTCondor takes care of jobs in this way
automatically following the policies given in configuration files.

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: