condor_cold_start - install and start Condor on this machine
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 ]
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 spooldirectories by specifying the archived versions.
Use the given architecturestr to fetch the installation package. The
string is in the format:
(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.
Use filename for name of the artifact file used to determine whether
the condor_master daemon is still alive.
The directory to install or find the Condor executables and
libraries. When not specified, the current working directory is
Create the Condor executedirectory from the given archive file.
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.
Overwrite previously installed files, if necessary.
The location of the globus installation on this machine. When not
specified /opt/globusis the directory used. This option is only
necessary when other options of the form -*archive are specified.
Display brief usage information and exit.
The directory where the Condor log, spool, and executedirectories
will be installed. Each running instance of Condor must have its own
Create the Condor log directory from the given archive file.
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.
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.
Run Condor from the specified installation directory without
installing it. It is possible to run several instantiations of
Condor from a single installation.
Install Condor without running it.
The ftp, http, gsiftp, or mounted file system directory where the
installation packages can be found (for example,
Create the Condor spool directory from the given archive file.
Use wget to fetch the log, spool, and executedirectories, if other
options of the form -*archive are specified. wget must be installed
on the machine and in the user’s path.
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.
condor_cold_start will exit with a status value of 0 (zero) upon
success, and non-zero otherwise.
To start a Condor installation on the current machine, using
http://www.example.com/Condor/deploymentas the installation site:
% condor_cold_start .br
Optionally if this instance of Condor requires a local configuration
% condor_cold_start .br
-site http://www.example.com/Condor/deployment .br
condor_cold_stop (on page ), filelock_midwife (on page ),
uniq_pid_midwife (on page ).
Condor Team, University of Wisconsin-Madison
Copyright (C) 1990-2009 Condor Team, Computer Sciences Department,
University of Wisconsin-Madison, Madison, WI. All Rights Reserved.
Licensed under the Apache License, Version 2.0.
See the Condor Version 7.2.4 Manual or
http://www.condorproject.org/licensefor additional notices. condor-