condor_cold_stop1
Shut down and uninstall a running condor instance
Usage
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
Overview
condor_cold_stop reliably shuts down and uninstall a running Condor instance. This program first uses condor_local_stopto reliably shut down the running Condor instance. It then uses condor_cleanup_localto 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 fileas the artifact file to determine whether the condor_masterdaemon 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 -stopare 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 -stopare 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 archivecan be a file path or a grid-ftp url.
-filelock
-
Determine whether the condor_masterdaemon 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_schedddaemon (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 -*archiveare 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 -cleanlocaloption 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 archivecan be a file path or a grid-ftp url.
-nogurl
-
Do not use globus-url-copyto store the archives. This implies that the archives can only be stored on mounted file systems.
-pid
-
Determine whether the condor_masterdaemon has exited using a unique process id undertaker. This option must match the corresponding option given to condor_cold_start.
-runlocalconfig file
-
Bind fileinto 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 archivecan 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 -stopare 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