condor_ cold_stop

reliably shut down and uninstall a running Condor instance

Synopsis

condor_ cold_stop -help

condor_ cold_stop [-force] [-basedir directory] [-localdir directory] [-runlocalconfig file] [-cleaninstall] [-cleanlocal] [-stop] [-logarchive archive] [-spoolarchive archive] [-execarchive archive] [-filelock] [-pid] [-artifact file] [-nogurl] [-globuslocation directory] -configfile file

Description

condor_ cold_stop reliably shuts down and uninstall a running Condor instance. This program first uses condor_ local_stop to reliably shut down the running Condor instance. It then uses condor_ cleanup_local to create and store archives of the log, spool, and execute directories. Its last task is to uninstall the Condor binaries and libraries using cleanup_release.

Options

-artifact file

Uses file as the artifact file to determine whether the condor_ master daemon is still alive.

-basedir directory

Directory where the Condor installation can be found. When not specified, the current working directory is assumed.

-cleaninstall

Remove the Condor installation. If none of the options -cleaninstall, -cleanlocal, or -stop are specified, the program behaves as though all of them have been provided.

-cleanlocal

The program will remove the log, spool, exec directories for this Condor instance. If none of the options -cleaninstall, -cleanlocal, or -stop are specified, the program behaves as though all of them have been provided.

-configfile file

The same configuration file path given to condor_ cold_start. This program assumes the file is in the installation directory or the current working directory.

-execarchive archive

The program will create a tar'ed and gzip'ed archive of the execute directory and stores it as archive. The archive can be a file path or a grid-ftp url.

-filelock

Determine whether the condor_ master daemon has exited using a file lock undertaker. This option must match the corresponding option given to condor_ cold_start.

-force

Ignore the status of the condor_ schedd daemon (whether it has jobs in the queue or not) when shutting down Condor.

-globuslocation directory

The directory containing the Globus installation. This option is required if any of the options of the form -*archive are used, and Globus is not installed in /opt/globus.

-localdir directory

Directory where the log, spool, and execute directories are stored for this running instance of Condor. Required if the -cleanlocal option is specified.

-logarchive archive

The program will create a tar'ed and gzip'ed archive of the log directory and stores it as archive. The archive can be a file path or a grid-ftp url.

-nogurl

Do not use globus-url-copy to store the archives. This implies that the archives can only be stored on mounted file systems.

-pid

Determine whether the condor_ master daemon has exited using a unique process id undertaker. This option must match the corresponding option given to condor_ cold_start.

-runlocalconfig file

Bind file into the configuration used by this instance of Condor. This option should the one provided to condor_ cold_start.

-spoolarchive archive

The program will create a tar'ed and gzip'ed archive of the spool directory and stores it as archive. The archive can be a file path or a grid-ftp url.

-stop

The program will shut down this running instance of Condor. If none of the options -cleaninstall, -cleanlocal, or -stop are specified, the program behaves as though all of them have been provided.

Exit Status

condor_ cold_stop will exit with a status value of 0 (zero) upon success, and non-zero otherwise.

Examples

To shut down a Condor instance on the target machine:

% condor_cold_stop -configfile condor_config.mobile

To shutdown a Condor instance and archive the log directory:

% condor_cold_stop -configfile condor_config.mobile \
  -logarchive /tmp/log.tar.gz

See Also

condor_ cold_start (on page ), filelock_undertaker (on page ), uniq_pid_undertaker (on page ).

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.