Next: condor_ convert_history
Up: 9. Command Reference Manual
Previous: condor_ config_val
Contents
Index
Subsections
condor_ configure
Configure or install Condor
condor_ configure
[--
help]
condor_ configure
[--
install[=<path/to/release.tar>] ]
[--
install-dir=<path>]
[--
local-dir=<path>]
[--
make-personal-condor]
[--
type = < submit, execute, manager >]
[--
central-manager = < hostname>]
[--
owner = < ownername >]
[--
make-personal-stork]
[--
stork]
[--
credd]
[--
verbose]
condor_ configure is a Perl script that installs and/or configures
Condor on Unix machines.
It will run with Perl 5.003 or more recent versions.
condor_ configure is designed to be run more than one time
where required.
It can install Condor (with a correct configuration),
or it can change the configuration files.
Note that changes in the configuration files do not result
in changes while Condor is running.
To effect changes while Condor is running,
it is necessary to further do condor_ reconfig or condor_ restart.
condor_ reconfig is required where the currently executing
daemons need to be informed of configuration changes.
condor_ restart is required where the options
--
make-personal-condor or
--
type
are used, since these affect which daemons are running.
Running condor_ configure with no options results in the
help screen being printed.
- --help
- Print help screen and exit
- --install
- Perform installation, assuming that
the current working directory contains the release.tar file.
Where a directory path is supplied,
it specifies that directory containing the release.tar file.
Without further options, the configuration is that of
a Personal Condor, a complete one-machine pool.
If used as an
upgrade within an existing installation directory, existing
configuration files and local directory are preserved.
- --install-dir=<path>
- Specifies the path
where Condor should be installed or the path where it already is
installed. The default is the current working directory.
- --local-dir=<path>
- Specifies the
location of the local directory, which is the directory that generally
contains the local (machine-specific) configuration file as well as the
directories where Condor daemons write their run-time information
(spool, log, execute).
This location is indicated by the LOCAL_DIR
variable in the configuration file.
When installing (that is, if --install is specified),
condor_ configure
will properly create the local directory in the location specified.
If none is specified, the default value is given by the evaluation of
$(RELEASE_DIR)/local.$(HOSTNAME).
During subsequent invocations of condor_ configure
(that is, without the --install option),
if the --local-dir option is specified, the new directory
will be created and the log, spool and execute
directories will be moved there from their current location.
- --make-personal-condor
- Installs and configures for
Personal Condor, a fully-functional, one-machine pool.
- --type= < submit, execute, manager >
- One
or more of the types may be listed.
This determines the roles that a machine may play in a pool.
In general, any machine can be a submit and/or execute machine,
and there is one central manager per pool.
In the case of a Personal Condor,
the machine fulfills all three of these roles.
- --central-manager=<hostname>
- Instructs
the current Condor installation to use the specified machine
as the central manager.
This modifies the configuration variables COLLECTOR_HOST
and NEGOTIATOR_HOST to point to the given host name).
The central manager machine's Condor configuration needs
to be independently configured to
act as a manager using the option --type=manager.
- --owner=<ownername>
- Set configuration
such that Condor daemons will be executed as the given owner.
This modifies the
ownership on the log, spool and execute
directories and sets the CONDOR_IDS value
in the configuration file,
to ensure that Condor daemons start up as the specified effective user.
See section 3.6.10 on
UIDs in Condor on page
for details.
This is only applicable when condor_ configure is run by root.
If not run as root, the owner is the user running
the condor_ configure command.
- --make-personal-stork
- Creates a
Personal Stork, using the condor_ credd daemon.
- --stork
- Configures the
Stork data placement server.
Use this option with the --credd option.
- --credd
- Configure the
the condor_ credd daemon (credential manager daemon).
- --verbose
- Print information about changes
to configuration variables as they occur.
condor_ configure will exit with a status value of 0 (zero) upon success,
and it will exit with a nonzero value upon failure.
Install Condor on the machine (machine1@cs.wisc.edu)
to be the pool's central manager.
On machine1,
within the directory that contains the unzipped Condor
distribution .tar.gz file:
% condor_configure --install --type=submit,execute,manager
This will allow the machine to submit and execute Condor jobs,
in addition to being the central manager of the pool.
To change the configuration such that
machine2@cs.wisc.edu is an execute-only machine
(that is, a dedicated computing node)
within a pool with central manager on machine1@cs.wisc.edu,
issue the command on that machine2@cs.wisc.edu
from within the directory where Condor is installed:
% condor_configure --central-manager=machine1@cs.wisc.edu --type=execute
To change the location of the LOCAL_DIR directory
in the configuration file, do (from the directory where Condor is installed):
% condor_configure --local-dir=/path/to/new/local/directory
This will move the log,spool,execute directories
to /path/to/new/local/directory from the current local directory.
Condor Team, University of Wisconsin-Madison
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.
Next: condor_ convert_history
Up: 9. Command Reference Manual
Previous: condor_ config_val
Contents
Index
condor-admin@cs.wisc.edu