condor_ cold_start

install and start Condor on this machine

Synopsis

condor_ cold_start -help

condor_ cold_start [-basedir directory] [-force] [-setuponly | -runonly] [-arch architecture] [-site repository] [-localdir directory] [-runlocalconfig file] [-logarchive archive] [-spoolarchive archive] [-execarchive archive] [-filelock] [-pid] [-artifact filename] [-wget] [-globuslocation directory] -configfile file

Description

condor_ cold_start installs and starts Condor on this machine, setting up or using a predefined configuration. In addition, it has the functionality to determine the local architecture if one is not specified. Additionally, this program can install pre-made log, execute, and/or spool directories by specifying the archived versions.

Options

-arch architecturestr

Use the given architecturestr to fetch the installation package. The string is in the format:

<condor_version>-<machine_arch>-<os_name>-<os_version>

(for example 6.6.7-i686-Linux-2.4). The portion of this string <condor_version> may be replaced with the string "latest" (for example, latest-i686-Linux-2.4) to substitute the most recent version of Condor.

-artifact filename

Use filename for name of the artifact file used to determine whether the condor_ master daemon is still alive.

-basedir directory

The directory to install or find the Condor executables and libraries. When not specified, the current working directory is assumed.

-execarchive archive

Create the Condor execute directory from the given archive file.

-filelock

Specifies that this program should use a POSIX file lock midwife program to create an artifact of the birth of a condor_ master daemon. A file lock undertaker can later be used to determine whether the condor_ master daemon has exited. This is the preferred option when the user wants to check the status of the condor_ master daemon from another machine that shares a distributed file system that supports POSIX file locking, for example, AFS.

-force

Overwrite previously installed files, if necessary.

-globuslocation directory

The location of the globus installation on this machine. When not specified /opt/globus is the directory used. This option is only necessary when other options of the form -*archive are specified.

-help

Display brief usage information and exit.

-localdir directory

The directory where the Condor log, spool, and execute directories will be installed. Each running instance of Condor must have its own local directory.

-logarchive archive

Create the Condor log directory from the given archive file.

-pid

This program is to use a unique process id midwife program to create an artifact of the birth of a condor_ master daemon. A unique pid undertaker can later be used to determine whether the condor_ master daemon has exited. This is the default option and the preferred method to check the status of the condor_ master daemon from the same machine it was started on.

-runlocalconfig file

A special local configuration file bound into the Condor configuration at runtime. This file only affects the instance of Condor started by this command. No other Condor instance sharing the same global configuration file will be affected.

-runonly

Run Condor from the specified installation directory without installing it. It is possible to run several instantiations of Condor from a single installation.

-setuponly

Install Condor without running it.

-site repository

The ftp, http, gsiftp, or mounted file system directory where the installation packages can be found (for example, www.cs.example.edu/packages/coldstart).

-spoolarchive archive

Create the Condor spool directory from the given archive file.

-wget

Use wget to fetch the log, spool, and execute directories, if other options of the form -*archive are specified. wget must be installed on the machine and in the user's path.

-configfile file

A required option to specify the Condor configuration file to use for this installation. This file can be located on an http, ftp, or gsiftp site, or alternatively on a mounted file system.

Exit Status

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

Examples

To start a Condor installation on the current machine, using http://www.example.com/Condor/deployment as the installation site:

% condor_cold_start \
  -configfile http://www.example.com/Condor/deployment/condor_config.mobile \
  -site http://www.example.com/Condor/deployment

Optionally if this instance of Condor requires a local configuration file condor_config.local:

% condor_cold_start \
  -configfile http://www.example.com/Condor/deployment/condor_config.mobile \
  -site http://www.example.com/Condor/deployment \
  -runlocalconfig condor_config.local

See Also

condor_ cold_stop (on page ), filelock_midwife (on page ), uniq_pid_midwife (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.