next up previous contents index
Next: 3.3 Configuration Up: 3. Administrators' Manual Previous: 3.1 Introduction   Contents   Index


3.2 Installation

This section contains the instructions for installing Condor at your Unix site.

There are two sets of instructions for installing Condor. They are identified as the older and the newer installation instructions. All discussion prior to installation is valid whether using the newer installation script or the older method. The installation will have a default configuration that can be customized. Sections of the manual that follow this one explain customization.

Read this entire section before starting installation.

Please read the copyright and disclaimer information in section [*] on page [*] of the manual, or in the file LICENSE.TXT, before proceeding. Installation and use of Condor is acknowledgment that you have read and agree to the terms.

3.2.1 Obtaining Condor

The first step to installing Condor is to download it from the Condor web site, The downloads are available from the downloads page, at

The platform-dependent Condor files are currently available from two sites. The main site is at the University of Wisconsin-Madison, Madison, Wisconsin, USA. A second site is the Istituto Nazionale di Fisica Nucleare Sezione di Bologna, Bologna, Italy. Please choose the site nearest to you.

Make note of the location of where you download the binary into.

The Condor binary distribution is packaged in the following 5 files and 2 directories:

directions on where to find Condor documentation
these installation directions
the licensing agreement. By installing Condor, you agree to the contents of this file
general information
the Perl script used to install and configure Condor
directory containing C, Fortran and C++ example programs to run with Condor
tar file of the release directory, which contains the Condor binaries and libraries

Before you install, please consider joining the condor-world mailing list. Traffic on this list is kept to an absolute minimum. It is only used to announce new releases of Condor. To subscribe, send a message to with the body:

   subscribe condor-world

3.2.2 Preparation

Before installation, make a few important decisions about the basic layout of your pool. The decisions answer the questions:

  1. What machine will be the central manager?
  2. What machines should be allowed to submit jobs?
  3. Will Condor run as root or not?
  4. Who will be administering Condor on the machines in your pool?
  5. Will you have a Unix user named condor and will its home directory be shared?
  6. Where should the machine-specific directories for Condor go?
  7. Where should the parts of the Condor system be installed?
  8. Am I using AFS?
  9. Do I have enough disk space for Condor?

1. What machine will be the central manager?

One machine in your pool must be the central manager. Install Condor on this machine first. This is the centralized information repository for the Condor pool, and it is also the machine that does match-making between available machines and submitted jobs. If the central manager machine crashes, any currently active matches in the system will keep running, but no new matches will be made. Moreover, most Condor tools will stop working. Because of the importance of this machine for the proper functioning of Condor, install the central manager on a machine that is likely to stay up all the time, or on one that will be rebooted quickly if it does crash.

Also consider network traffic and your network layout when choosing your central manager. All the daemons send updates (by default, every 5 minutes) to this machine. Memory requirements for the central manager differ by the number of machines in the pool. A pool with up to about 100 machines will require approximately 25 Mbytes of memory for the central manager's tasks. A pool with about 1000 machines will require approximately 100 Mbytes of memory for the central manager's tasks.

A faster CPU will improve the time to do matchmaking.

2. Which machines should be allowed to submit jobs?

Condor can restrict the machines allowed to submit jobs. Alternatively, it can allow any machine the network allows to connect to a submit machine to submit jobs. If the Condor pool is behind a firewall, and all machines inside the firewall are trusted, the HOSTALLOW_WRITE configuration entry can be set to *. Otherwise, it should be set to reflect the set of machines permitted to submit jobs to this pool. Condor tries to be secure by default, so out of the box, the configuration file ships with an invalid definition for this configuration variable. This invalid value allows no machine to connect and submit jobs, so after installation, change this entry. Look for the entry defined with the value YOU_MUST_CHANGE_THIS_INVALID_CONDOR_CONFIGURATION_VALUE.

3. Will Condor run as root or not?

Start up the Condor daemons as the Unix user root. Without this, Condor can do very little to enforce security and policy decisions. You can install Condor as any user, however there are both serious security and performance consequences. Please see section 3.6.12 on page [*] in the manual for the details and ramifications of running Condor as a Unix user other than root.

4. Who will administer Condor?

Either root will be administering Condor directly, or someone else would be acting as the Condor administrator. If root has delegated the responsibility to another person but doesn't want to grant that person root access, root can specify a condor_config.root file that will override settings in the other condor configuration files. This way, the global condor_config file can be owned and controlled by whoever is condor-admin, and the condor_config.root can be owned and controlled only by root. Settings that would compromise root security (such as which binaries are started as root) can be specified in the condor_config.root file while other settings that only control policy or condor-specific settings can still be controlled without root access.

5. Will you have a Unix user named condor, and will its home directory be shared?

To simplify installation of Condor, create a Unix user named condor on all machines in the pool. The Condor daemons will create files (such as the log files) owned by this user, and the home directory can be used to specify the location of files and directories needed by Condor. The home directory of this user can either be shared among all machines in your pool, or could be a separate home directory on the local partition of each machine. Both approaches have advantages and disadvantages. Having the directories centralized can make administration easier, but also concentrates the resource usage such that you potentially need a lot of space for a single shared home directory. See the section below on machine-specific directories for more details.

If you choose not to create a user named condor, then you must specify either via the CONDOR_IDS environment variable or the CONDOR_IDS config file setting which uid.gid pair should be used for the ownership of various Condor files. See section 3.6.12 on UIDs in Condor on page [*] in the Administrator's Manual for details.

6. Where should the machine-specific directories for Condor go?

Condor needs a few directories that are unique on every machine in your pool. These are spool, log, and execute. Generally, all three are subdirectories of a single machine specific directory called the local directory (specified by the LOCAL_DIR macro in the configuration file). Each should be owned by the user that Condor is to be run as.

If you have a Unix user named condor with a local home directory on each machine, the LOCAL_DIR could just be user condor's home directory (LOCAL_DIR = $(TILDE) in the configuration file). If this user's home directory is shared among all machines in your pool, you would want to create a directory for each host (named by host name) for the local directory (for example, LOCAL_DIR = $(TILDE)/hosts/$(HOSTNAME)). If you do not have a condor account on your machines, you can put these directories wherever you'd like. However, where to place them will require some thought, as each one has its own resource needs:

This is the directory that acts as the current working directory for any Condor jobs that run on a given execute machine. The binary for the remote job is copied into this directory, so there must be enough space for it. (Condor will not send a job to a machine that does not have enough disk space to hold the initial binary). In addition, if the remote job dumps core for some reason, it is first dumped to the execute directory before it is sent back to the submit machine. So, put the execute directory on a partition with enough space to hold a possible core file from the jobs submitted to your pool.

The spool directory holds the job queue and history files, and the checkpoint files for all jobs submitted from a given machine. As a result, disk space requirements for the spool directory can be quite large, particularly if users are submitting jobs with very large executables or image sizes. By using a checkpoint server (see section 3.8 on Installing a Checkpoint Server on page [*] for details), you can ease the disk space requirements, since all checkpoint files are stored on the server instead of the spool directories for each machine. However, the initial checkpoint files (the executables for all the clusters you submit) are still stored in the spool directory, so you will need some space, even with a checkpoint server.

Each Condor daemon writes its own log file, and each log file is placed in the log directory. You can specify what size you want these files to grow to before they are rotated, so the disk space requirements of the directory are configurable. The larger the log files, the more historical information they will hold if there is a problem, but the more disk space they use up. If you have a network file system installed at your pool, you might want to place the log directories in a shared location (such as /usr/local/condor/logs/$(HOSTNAME)), so that you can view the log files from all your machines in a single location. However, if you take this approach, you will have to specify a local partition for the lock directory (see below).

Condor uses a small number of lock files to synchronize access to certain files that are shared between multiple daemons. Because of problems encountered with file locking and network file systems (particularly NFS), these lock files should be placed on a local partition on each machine. By default, they are placed in the log directory. If you place your log directory on a network file system partition, specify a local partition for the lock files with the LOCK parameter in the configuration file (such as /var/lock/condor).

Generally speaking, it is recommended that you do not put these directories (except lock) on the same partition as /var, since if the partition fills up, you will fill up /var as well. This will cause lots of problems for your machines. Ideally, you will have a separate partition for the Condor directories. Then, the only consequence of filling up the directories will be Condor's malfunction, not your whole machine.

7. Where should the parts of the Condor system be installed?

Configuration Files
There are a number of configuration files that allow you different levels of control over how Condor is configured at each machine in your pool. The global configuration file is shared by all machines in the pool. For ease of administration, this file should be located on a shared file system, if possible. In addition, there is a local configuration file for each machine, where you can override settings in the global file. This allows you to have different daemons running, different policies for when to start and stop Condor jobs, and so on. You can also have configuration files specific to each platform in your pool. See section 3.12.2 on page [*] about Configuring Condor for Multiple Platforms for details.

In addition, because we recommend that you start the Condor daemons as root, we allow you to create configuration files that are owned and controlled by root that will override any other Condor settings. This way, if the Condor administrator is not root, the regular Condor configuration files can be owned and writable by condor-admin, but root does not have to grant root access to this person. See section [*] on page [*] in the manual for a detailed discussion of the root configuration files, if you should use them, and what settings should be in them.

In general, there are a number of places that Condor will look to find its configuration files. The first file it looks for is the global configuration file. These locations are searched in order until a configuration file is found. If none contain a valid configuration file, Condor will print an error message and exit:

  1. File specified in the CONDOR_CONFIG environment variable
  2. /etc/condor/condor_config
  3. ~condor/condor_config
  4. $(GLOBUS_LOCATION)/etc/condor_config

If you specify a file in the CONDOR_CONFIG environment variable and there's a problem reading that file, Condor will print an error message and exit right away, instead of continuing to search the other options. However, if no CONDOR_CONFIG environment variable is set, Condor will search through the other options.

Next, Condor tries to load the local configuration file(s). The only way to specify the local configuration file(s) is in the global configuration file, with the LOCAL_CONFIG_FILE macro. If that macro is not set, no local configuration file is used. This macro can be a list of files or a single file.

The root configuration files come in last. The global file is searched for in the following places:

  1. /etc/condor/condor_config.root
  2. ~condor/condor_config.root

The local root configuration file(s) are found with the LOCAL_ROOT_CONFIG_FILE macro. If that is not set, no local root configuration file is used. This macro can be a list of files or a single file.

Release Directory

Every binary distribution contains a release.tar file that contains five subdirectories: bin, etc, lib, sbin, and libexec. Wherever you choose to install these five directories we call the release directory (specified by the RELEASE_DIR macro in the configuration file). Each release directory contains platform-dependent binaries and libraries, so you will need to install a separate one for each kind of machine in your pool. For ease of administration, these directories should be located on a shared file system, if possible.

  • User Binaries:

    All of the files in the bin directory are programs the end Condor users should expect to have in their path. You could either put them in a well known location (such as /usr/local/condor/bin) which you have Condor users add to their PATH environment variable, or copy those files directly into a well known place already in the user's PATHs (such as /usr/local/bin). With the above examples, you could also leave the binaries in /usr/local/condor/bin and put in soft links from /usr/local/bin to point to each program.

  • System Binaries:

    All of the files in the sbin directory are Condor daemons and agents, or programs that only the Condor administrator would need to run. Therefore, add these programs only to the PATH of the Condor administrator.

  • Private Condor Binaries:

    All of the files in the libexec directory are Condor programs that should never be run by hand, but are only used internally by Condor.

  • lib Directory:

    The files in the lib directory are the Condor libraries that must be linked in with user jobs for all of Condor's checkpointing and migration features to be used. lib also contains scripts used by the condor_ compile program to help re-link jobs with the Condor libraries. These files should be placed in a location that is world-readable, but they do not need to be placed in anyone's PATH. The condor_ compile script checks the configuration file for the location of the lib directory.

  • etc Directory:

    etc contains an examples subdirectory which holds various example configuration files and other files used for installing Condor. etc is the recommended location to keep the master copy of your configuration files. You can put in soft links from one of the places mentioned above that Condor checks automatically to find its global configuration file.


The documentation provided with Condor is currently available in HTML, Postscript and PDF (Adobe Acrobat). It can be locally installed wherever is customary at your site. You can also find the Condor documentation on the web at:

7. Am I using AFS?

If you are using AFS at your site, be sure to read the section 3.12.1 on page [*] in the manual. Condor does not currently have a way to authenticate itself to AFS. A solution is not ready for Version 6.8.7. This implies that you are probably not going to want to have the LOCAL_DIR for Condor on AFS. However, you can (and probably should) have the Condor RELEASE_DIR on AFS, so that you can share one copy of those files and upgrade them in a centralized location. You will also have to do something special if you submit jobs to Condor from a directory on AFS. Again, read manual section 3.12.1 for all the details.

8. Do I have enough disk space for Condor?

Condor takes up a fair amount of space. This is another reason why it is a good idea to have it on a shared file system. The size requirements for the downloads are given on the downloads page. They currently vary from about 20 Mbytes (statically linked HP Unix on a PA RISC) to more than 50 Mbytes (dynamically linked Irix on an SGI).

In addition, you will need a lot of disk space in the local directory of any machines that are submitting jobs to Condor. See question 6 above for details on this.

3.2.3 Newer Unix Installation Procedure

The Perl script condor_ configure installs Condor. Command-line arguments specify all needed information to this script. The script can be executed multiple times, to modify or further set the configuration. condor_ configure has been tested using Perl 5.003. Use this or a more recent version of Perl.

After download, all the files are in a compressed, tar format. They need to be untarred, as

  tar xzf completename.tar.gz
After untarring, the directory will have the Perl script condor_ configure, as well as a second tar file called release.tar. condor_ configure works on release.tar.

condor_ configure is completely command-line driven; it is not interactive. Several command-line arguments are always needed with condor_ configure. The argument

specifies the path to the Condor release tarball. The argument
specifies the path to the install directory. The argument
specifies the path to the local directory.

The -type option to condor_ configure specifies one or more of the roles that a machine may take on within the Condor pool: central manager, submit or execute. These options are given in a comma separated list. So, if a machine is both a submit and execute machine, the proper command-line option is


Configure Condor on the central manager machine first. If Condor will run as root in this pool (Item 3 above), run condor_ configure as root, and it will install and set the file permissions correctly. On the central manager machine, run condor_ configure as follows.

% condor_configure --install=r.tar --install-dir=~condor \
	--local-dir=/scratch/condor --type=manager

The central manager can also be a submit point or and execute machine, but this is only recommended for very small pools. If this is the case, the -type option changes to manager,execute or manager,submit or manager,submit,execute.

After the central manager is installed, the execute and submit machines should then be configured. Decisions about whether to run Condor as root should be consistent throughout the pool. For each machine in the pool, run

% condor_configure --install=r.tar --install-dir=~condor \
	--local-dir=/scratch/condor --type=execute,submit

See the condor_ configure manual page in section 9 on page [*] for details.

Please skip to section 3.2.5 for final instructions on configuring and starting Condor.

3.2.4 Older Unix Installation Procedure


After download, all the files are in a compressed, tar format. They need to be untarred, as

        tar xzf completename.tar.gz

To install Condor, use one or both of the scripts provided to help you: condor_ install and condor_ init. Run these scripts as the user that you are going to run the Condor daemons as. First, run condor_ install on the machine that will be a file server for shared files used by Condor, such as the release directory, and possibly the condor user's home directory. When you do, choose the ``full-install'' option in step #1 described below.

Once you have run condor_ install on a file server to set up your release directory and configure Condor for your site, you should run condor_ init on any other machines in your pool to create any locally used files that are not created by condor_ install. In the most simple case, where nearly all of Condor is installed on a shared file system, even though condor_ install will create nearly all the files and directories you need, you will still need to use condor_ init to create the LOCK directory on the local disk of each machine. If you have a shared release directory, but the LOCAL_DIR is local on each machine, condor_ init will create all the directories and files needed in LOCAL_DIR. In addition, condor_ init will create any soft links on each machine that are needed so that Condor can find its global configuration file.

If you do not have a shared file system, you need to run condor_ install on each machine in your pool to set up Condor. In this case, there is no need to run condor_ init at all.

In addition, you will want to run condor_ install on your central manager machine if that machine is different from your file server, using the ``central-manager'' option in step #1 described below. Run condor_ install on your file server first, then on your central manager. If this step fails for some reason (NFS permissions, etc), you can do it manually quite easily. All this does is copy the condor_config.local.central.manager file from <release_dir>/etc/examples to the proper location for the local configuration file of your central manager machine. If your central manager is an Alpha or an SGI, you might want to add KBDD to the $(DAEMON_LIST) macro. See section 3.3 Configuring Condor on page [*] of the manual for details.

condor_ install assumes you have perl installed in /usr/bin/perl. If this is not the case, you can either edit the script to put in the right path, or you will have to invoke perl directly from your shell (assuming perl is in your PATH):

% perl condor_install

condor_ install breaks down the installation procedure into various steps. Each step is clearly numbered. The following section explains what each step is for, and suggests how to answer the questions condor_ install will ask you for each one. condor_ install, step-by-step

STEP 1: What type of Condor installation do you want?

There are three types of Condor installation you might choose: 'submit-only', 'full-install', and 'central-manager'. A submit-only machine can submit jobs to a Condor pool, but Condor jobs will not run on it. A full-install machine can both submit and run Condor jobs.

If you are planning to run Condor jobs on your machines, you should either install and run Condor as root, or as the Unix user condor.

If you are planning to set up a submit-only machine, you can either install Condor machine-wide as root or user condor, or, you can install Condor as yourself into your home directory.

The other possible installation type is setting up a machine as a central manager. If you do a full-install and you say that you want the local host to be your central manager, this step will be done automatically. You should only choose the central-manager option at step 1 if you have already run condor_ install on your file server and you now want to run condor_ install on a different machine that will be your central manager.

STEP 2: How many machines are you setting up this way?

If you are installing Condor for multiple machines and you have a shared file system, then condor_ install will prompt you for the host names of each machine you want to add to your Condor pool. If you do not have a shared file system, you will have to run condor_ install locally on each machine, so condor_ install does not ask for the names. If you provide a list, it will use the names to automatically create directories and files later. At the end, condor_ install will dump out this list to a roster file which can be used by scripts to help maintain your Condor pool.

If you are only installing Condor on 1 machine, you would answer no to the first question, and move on.

STEP 3: Install the Condor release directory
The release directory contains five subdirectories: bin, etc, lib, libexec and sbin. bin contains user-level executable programs. etc is the recommended location for your Condor configuration files, and it also includes an examples directory with default configuration files and other default files used for installing Condor. lib contains libraries to link Condor user programs and scripts used by the Condor system. sbin contains all administrative executable programs and the Condor daemons. libexec contains programs that only Condor needs to execute.

If you have multiple machines with a shared file system that will be running Condor, put the release directory on that shared file system so you only have one copy of all the binaries, and so that when you update them, you can do so in one place. Note that the release directory is architecture dependent, so download separate binary distributions for every platform in your pool.

condor_ install tries to find an already installed release directory. If it cannot find one, it asks if you have installed one already. If you have not installed one, it tries to do so for you by untarring the release.tar file from the binary distribution.

NOTE: If you are only setting up a central manager (you chose 'central manager' in STEP 1), STEP 3 is the last question you will need to answer.

STEP 4: How and where should Condor send e-mail if things go wrong?

Various parts of Condor will send e-mail to a condor administrator if something goes wrong that needs human attention. You will need to specify the e-mail address of this administrator.

You also specify the full path to a mail program that Condor will use to send the e-mail. This program needs to understand the -s option, to specify a subject for the outgoing message. The default on most platforms will probably be correct. On Linux machines, since there is such variation in Linux distributions and installations, verify that the default works. If the script complains that it cannot find the mail program that was specified, try

% which mail
to see what mail program is currently in your PATH. If there is none, try
% which mailx
If you still cannot find anything, ask your system administrator. Verify that the program you use supports -s. The man page for that program will probably tell you.

STEP 5: File system and UID domains.

Condor does not depend on a shared file system and common UID space for running jobs outside the standard universe. Jobs can specify file transfer within the submit description file. See section 2.5.4 on page [*] for information on properly setting up file transfer for jobs.

To utilize the convenience of a shared file system (such as NFS), a common UID space is needed. This is one in which there is a unique mapping of user names to UIDs across all machines in the common UID space. It is important to correctly configure Condor with respect to a shared file system. For complete details on what these settings do and how you should answer the questions, read section 3.3.7, Shared File System Configuration File Entries'', on page [*].

You will be asked if you have a shared file system. If so, condor_ install will configure your FILESYSTEM_DOMAIN setting to be set to the domain name of the machine running condor_ install. If not, FILESYSTEM_DOMAIN will be set to $(FULL_HOSTNAME), indicating that each machine is in its own domain.

For the UID domain, Condor needs to know if all user names across all the machines in the pool have a unique UID. If so, UID_DOMAIN will be set to the domain name of the machine running condor_ install. If not, UID_DOMAIN will be set to $(FULL_HOSTNAME), indicating that each machine is in its own domain.

If you have a common UID_DOMAIN, condor_ install will ask if you have a soft UID domain, meaning that although you have unique UIDs, not every machine in your pool has all the users in their individual password files. Please see the description of SOFT_UID_DOMAIN in section 3.3.7 on page [*] for details.

STEP 6: Java Universe support in Condor.

Condor has the ability to run Java programs with remote i/o, but no checkpointing. If you would like to enable this feature in Condor, then select yes for enabling of Java Universe. The installer will try to determine if you have a valid JVM and prompt you if nothing suitable can be found. If you do not care to use the Java Universe, then it is safe to say no here.

STEP 7: Where should public programs be installed?

It is recommended that you install the user-level Condor programs in the release directory, (where they go by default). This way, when you want to install a new version of the Condor binaries, you can just replace your release directory and everything will be updated at once. So, one option is to have Condor users add <release_dir>/bin to their PATH, so that they can access the programs. However, we recommend putting in soft links from some directory already in their PATH (such as /usr/local/bin) that point back to the Condor user programs. condor_ install will do this for you. All you do is tell it what directory to put these links into. This way, users do not have to change their PATH to use Condor, and you can still have the binaries installed in their own location.

If you are installing Condor as neither root nor condor, there is a perl script wrapper to all the Condor tools that is created which sets some appropriate environment variables and automatically passes certain options to the tools. This is all created automatically by condor_ install. So, you need to tell condor_ install where to put this perl script. The script itself is linked to itself with many different names, since it is the name that determines the behavior of the script. This script should go somewhere that is in your PATH already, if possible (such as ~bin).

At this point, the remaining steps differ based on the whether the installation is a full install or a submit-only. Skip to the appropriate section below, based on the kind of installation. Full Install

STEP 8: What machine will be your central manager?

Type in the full host name of the machine you have chosen for your central manager. If condor_ install cannot find information about the host you typed by querying your name server, it will print out an error message and ask you to confirm.

STEP 9: Where will the local directory go?

This is the directory discussed in question 5 of the installation introduction. condor_ install tries to make some educated guesses as to what directory you want to use for the purpose. Agree to the correct guess, or (when condor_ install has run out of guesses) type in what you want. Since this directory needs to be unique, it is common to use the host name of each machine in its name. When typing in your own path, you can use '$(HOSTNAME)' which condor_ install (and the Condor configuration files) will expand to the host name of the machine you are currently on. condor_ install will try to create the corresponding directories for all the machines you told it about in STEP 2 above.

Once you have selected the local directory, condor_ install creates all the needed subdirectories of each one with the proper permissions. They should have the following permissions and ownerships:

     drwxr-xr-x   2 condor   root         1024 Mar  6 01:30 execute/
     drwxr-xr-x   2 condor   root         1024 Mar  6 01:30 log/
     drwxr-xr-x   2 condor   root         1024 Mar  6 01:30 spool/

If your local directory is on a shared file system, condor_ install will prompt you for the location of your lock files, as discussed in question #5 above. In this case, when condor_ install is finished, you will have to run condor_ init on each machine in your pool to create the lock directory before you can start up Condor.

STEP 10: Where will the local (machine-specific) configuration files go?

As discussed in question STEP 6 above, there are a few different levels of Condor configuration files. There is the global configuration file that will be installed in <release_dir>/etc/condor_config, and there are machine-specific, or local configuration files, that override the settings in the global file. If you are installing on multiple machines or are configuring your central manager machine, you must select a location for your local configuration files.

The two main options are to have a single directory that holds all the local configuration files, each one named $(HOSTNAME).local, or to have the local configuration files go into the individual local directories for each machine. Given a shared file system, we recommend the first option, since it makes it easier to configure your pool from a centralized location.

STEP 11: How shall Condor find its configuration file?

Since there are a few known places Condor looks to find your configuration file, we recommend that you put a soft link from one of them to point to <release_dir>/etc/condor_config. This way, you can keep your Condor configuration in a centralized location, but all the Condor daemons and tools will be able to find their configuration files. Alternatively, you can set the CONDOR_CONFIG environment variable to contain <release_dir>/etc/condor_config.

condor_ install will ask you if you want to create a soft link from either of the two fixed locations that Condor searches.

Once you have completed STEP 11, you are done. condor_ install prints out a messages describing what to do next. Please skip to section 3.2.5. Submit Only

A submit-only installation of Condor implies that the machine will be submitting jobs to one or more established Condor pools. Configuration for this installation needs to account for the other pools.

For the submit-only installation, STEP 6 continues and completes the installation.

STEP 6: continued.
A submit-only machine has the option of submission to more than one Condor pool. The full host name of the central manager is required for each pool. The first entered becomes the default for start up and job submission.

There is a separate configuration file for each pool. The location of each file is specified.

Identification of each pool requires a unique name. A final question sets a name for each pool. The name will be the argument for -pool command line options.

3.2.5 Condor is installed Under Unix ... now what?

Now that Condor has been installed on your machine(s), there are a few things you should check before you start up Condor.

  1. Read through the <release_dir>/etc/condor_config file. There are a lot of possible settings and you should at least take a look at the first two main sections to make sure everything looks okay. In particular, you might want to set up security for Condor. See the section 3.6.1 on page [*] to learn how to do this.

  2. Condor can monitor the activity of your mouse and keyboard, provided that you tell it where to look. You do this with the CONSOLE_DEVICES entry in the condor_ startd section of the configuration file. On most platforms, reasonable defaults are provided. For example, the default device for the mouse on Linux is 'mouse', since most Linux installations have a soft link from /dev/mouse that points to the right device (such as tty00 if you have a serial mouse, psaux if you have a PS/2 bus mouse, etc). If you do not have a /dev/mouse link, you should either create one (you will be glad you did), or change the CONSOLE_DEVICES entry in Condor's configuration file. This entry is a comma separated list, so you can have any devices in /dev count as 'console devices' and activity will be reported in the condor_ startd's ClassAd as ConsoleIdleTime.

  3. (Linux only) Condor needs to be able to find the utmp file. According to the Linux File System Standard, this file should be /var/run/utmp. If Condor cannot find it there, it looks in /var/adm/utmp. If it still cannot find it, it gives up. So, if your Linux distribution places this file somewhere else, be sure to put a soft link from /var/run/utmp to point to the real location.

To start up the Condor daemons, execute <release_dir>/sbin/condor_master. This is the Condor master, whose only job in life is to make sure the other Condor daemons are running. The master keeps track of the daemons, restarts them if they crash, and periodically checks to see if you have installed new binaries (and if so, restarts the affected daemons).

If you are setting up your own pool, you should start Condor on your central manager machine first. If you have done a submit-only installation and are adding machines to an existing pool, the start order does not matter.

To ensure that Condor is running, you can run either:

        ps -ef | egrep condor_
        ps -aux | egrep condor_
depending on your flavor of Unix. On a central manager machine that can submit jobs as well as execute them, there will be processes for: On a central manager machine that does not submit jobs nor execute them, there will be processes for: For a machine that only submits jobs, there will be processes for: For a machine that only executes jobs, there will be processes for: (NOTE: On Alphas, there will also be a condor_ kbdd - see section 3.12.4 on page [*] of the manual for details.)

Once you are sure the Condor daemons are running, check to make sure that they are communicating with each other. You can run condor_ status to get a one line summary of the status of each machine in your pool.

Once you are sure Condor is working properly, you should add condor_ master into your startup/bootup scripts (i.e. /etc/rc ) so that your machine runs condor_ master upon bootup. condor_ master will then fire up the necessary Condor daemons whenever your machine is rebooted.

If your system uses System-V style init scripts, you can look in <release_dir>/etc/examples/condor.boot for a script that can be used to start and stop Condor automatically by init. Normally, you would install this script as /etc/init.d/condor and put in soft link from various directories (for example, /etc/rc2.d) that point back to /etc/init.d/condor. The exact location of these scripts and links will vary on different platforms.

If your system uses BSD style boot scripts, you probably have an /etc/rc.local file. Add a line to start up <release_dir>/sbin/condor_master.

Now that the Condor daemons are running, there are a few things you can and should do:

  1. (Optional) Do a full install for the condor_ compile script. condor_ compile assists in linking jobs with the Condor libraries to take advantage of all of Condor's features. As it is currently installed, it will work by placing it in front of any of the following commands that you would normally use to link your code: gcc, g++, g77, cc, acc, c89, CC, f77, fort77 and ld. If you complete the full install, you will be able to use condor_ compile with any command whatsoever, in particular, make. See section 3.12.3 on page [*] in the manual for directions.

  2. Try building and submitting some test jobs. See examples/README for details.

  3. If your site uses the AFS network file system, see section 3.12.1 on page [*] in the manual.

  4. We strongly recommend that you start up Condor (run the condor_ master daemon) as user root. If you must start Condor as some user other than root, see section 3.6.12 on page [*].

3.2.6 Installation on Windows

This section contains the instructions for installing the Microsoft Windows version of Condor at your site. The install program will set you up with a slightly customized configuration file that you can further customize after the installation has completed.

Please read the copyright and disclaimer information in section [*] on page [*] of the manual, or in the file LICENSE.TXT, before proceeding. Installation and use of Condor is acknowledgement that you have read and agreed to these terms.

Be sure that the Condor tools that get run are of the same version as the daemons installed. If they were not (such as 6.5.3 daemons, when running 6.4 condor_ submit), then things will not work. There may be errors generated by the condor_ schedd daemon (in the log). It is likely that a job would be correctly placed in the queue, but the job will never run.

The Condor executable for distribution is packaged in a single file such as:


This file is approximately 80 Mbytes in size, and may be removed once Condor is fully installed.

Before installing Condor, please consider joining the condor-world mailing list. Traffic on this list is kept to an absolute minimum. It is only used to announce new releases of Condor. To subscribe, follow the directions given at Installation Requirements Preparing to Install Condor under Windows

Before you install the Windows version of Condor at your site, there are two major decisions to make about the basic layout of your pool.

  1. What machine will be the central manager?
  2. Do I have enough disk space for Condor?

If you feel that you already know the answers to these questions, skip to the Windows Installation Procedure section below, section 3.2.6 on page [*]. If you are unsure, read on. Installation Procedure using the included Set Up Program

Installation of Condor must be done by a user with administrator privileges. After installation, the Condor services will be run under the local system account. When Condor is running a user job, however, it will run that User job with normal user permissions.

Download Condor, and start the installation process by running the file (or by double clicking on the file). The Condor installation is completed by answering questions and choosing options within the following steps.

If Condor is already installed.

For upgrade purposes, you may be running the installation of Condor after it has been previously installed. In this case, a dialog box will appear before the installation of Condor proceeds. The question asks if you wish to preserve your current Condor configuration files. Answer yes or no, as appropriate.

If you answer yes, your configuration files will not be changed, and you will proceed to the point where the new binaries will be installed.

If you answer no, then there will be a second question that asks if you want to use answers given during the previous installation as default answers.

STEP 1: License Agreement.

The first step in installing Condor is a welcome screen and license agreement. You are reminded that it is best to run the installation when no other Windows programs are running. If you need to close other Windows programs, it is safe to cancel the installation and close them. You are asked to agree to the license. Answer yes or no. If you should disagree with the License, the installation will not continue.

After agreeing to the license terms, the next Window is where fill in your name and company information, or use the defaults as given.

STEP 2: Condor Pool Configuration.

The Condor installation will require different information depending on whether the installer will be creating a new pool, or joining an existing one.

If you are creating a new pool, the installation program requires that this machine is the central manager. For the creation of a new Condor pool, you will be asked some basic information about your new pool:

Name of the pool
of this machine.
Size of pool
Condor needs to know if this a Personal Condor installation, or if there will be more than one machine in the pool. A Personal Condor pool implies that there is only one machine in the pool. For Personal Condor, several of the following steps are omitted as noted.

If you are joining an existing pool, all the installation program requires is the hostname of the central manager for your pool.

STEP 3: This Machine's Roles.

This step is omitted for the installation of Personal Condor.

Each machine within a Condor pool may either submit jobs or execute submitted jobs, or both submit and execute jobs. This step allows the installation on this machine to choose if the machine will only submit jobs, only execute submitted jobs, or both. The common case is both, so the default is both.

STEP 4: Where will Condor be installed?

The next step is where the destination of the Condor files will be decided. It is recommended that Condor be installed in the location shown as the default in the dialog box: C:\Condor.

Installation on the local disk is chosen for several reasons.

The Condor services run as local system, and within Microsoft Windows, local system has no network privileges. Therefore, for Condor to operate, Condor should be installed on a local hard drive as opposed to a network drive (file server).

The second reason for installation on the local disk is that the Windows usage of drive letters has implications for where Condor is placed. The drive letter used must be not change, even when different users are logged in. Local drive letters do not change under normal operation of Windows.

While it is strongly discouraged, it may be possible to place Condor on a hard drive that is not local, if a dependency is added to the service control manager such that Condor starts after the required file services are available.

STEP 5: Where is the Java Virtual Machine?
While not required, it is possible for Condor to run jobs in the Java universe. In order for Condor to have support for java, you must supply a path to java.exe on your system. The installer will tell you if the path is invalid before proceeding to the next step. To disable the Java universe, simply leave this field blank.

STEP 6: Where should Condor send e-mail if things go wrong?

Various parts of Condor will send e-mail to a Condor administrator if something goes wrong and requires human attention. You specify the e-mail address and the SMTP relay host of this administrator. Please pay close attention to this email since it will indicate problems in your Condor pool.

STEP 7: The domain.

This step is omitted for the installation of Personal Condor.

Enter the machine's accounting (or UID) domain. On this version of Condor for Windows, this setting only used for User priorities (see section 3.4 on page [*]) and to form a default email address for the user.

STEP 8: Access permissions.
This step is omitted for the installation of Personal Condor.

Machines within the Condor pool will need various types of access permission. The three categories of permission are read, write, and administrator. Enter the machines to be given access permissions.

Read access allows a machine to obtain information about Condor such as the status of machines in the pool and the job queues. All machines in the pool should be given read access. In addition, giving read access to * will allow the Condor team to obtain information about your Condor pool in the event that debugging is needed.
All machines in the pool should be given write access. It allows the machines you specify to send information to your local Condor daemons, for example, to start a Condor Job. Note that for a machine to join the Condor pool, it must have both read and write access to all of the machines in the pool.
A machine with administrator access will be allowed more extended permission to to things such as change other user's priorities, modify the job queue, turn Condor services on and off, and restart Condor. The central manager should be given administrator access and is the default listed. This setting is granted to the entire machine, so care should be taken not to make this too open.

For more details on these access permissions, and others that can be manually changed in your condor_config file, please see the section titled Setting Up IP/Host-Based Security in Condor in section section 3.6.10 on page [*].

STEP 9: Job Start Policy.
Condor will execute submitted jobs on machines based on a preference given at installation. Three options are given, and the first is most commonly used by Condor pools. This specification may be changed or refined in the machine ClassAd requirements attribute.

The three choices:

After 15 minutes of no console activity and low CPU activity.
Always run Condor jobs.
After 15 minutes of no console activity.

Console activity is the use of the mouse or keyboard. For instance, if you are reading this document online, and are using either the mouse or the keyboard to change your position, you are generating Console activity.

Low CPU activity is defined as a load of less than 30% (and is configurable in your condor_config file). If you have a multiple processor machine, this is the average percentage of CPU activity for both processors.

For testing purposes, it is often helpful to use use the Always run Condor jobs option. For production mode, however, most people chose the After 15 minutes of no console activity and low CPU activity.

STEP 10: Job Vacate Policy.
This step is omitted if Condor jobs are always run as the option chosen in STEP 9.

If Condor is executing a job and the user returns, Condor will immediately suspend the job, and after five minutes Condor will decide what to do with the partially completed job. There are currently two options for the job.

The job is killed 5 minutes after your return.
The job is suspended immediately once there is console activity. If the console activity continues, then the job is vacated (killed) after 5 minutes. Since this version does not include check-pointing, the job will be restarted from the beginning at a later time. The job will be placed back into the queue.
Suspend job, leaving it in memory.
The job is suspended immediately. At a later time, when the console activity has stopped for ten minutes, the execution of Condor job will be resumed (the job will be unsuspended). The drawback to this option is that since the job will remain in memory, it will occupy swap space. In many instances, however, the amount of swap space that the job will occupy is small.

So which one do you choose? Killing a job is less intrusive on the workstation owner than leaving it in memory for a later time. A suspended job left in memory will require swap space, which could possibly be a scarce resource. Leaving a job in memory, however, has the benefit that accumulated run time is not lost for a partially completed job.

STEP 11: Review entered information.
Check that the entered information is correctly entered. You have the option to return to previous dialog boxes to fix entries. Unattended Installation Procedure using the included Set Up Program

This section details how to run the Condor for Windows installer in an unattended batch mode, i.e. completely from the command prompt without the GUI interface.

The Condor for Windows installer uses the Microsoft Installer (MSI) technology, and can be configured for unattended installs just like any other ordinary MSI installer.

The following is a sample batch file that is used to set all the properties necessary for an unattended install.

@echo on
set ARGS=
set ARGS=%ARGS% SMTPSERVER="smtp.localhost"
set ARGS=%ARGS% JVMLOCATION="C:\Windows\system32\java.exe"

msiexec /qb /l* condor-install-log.txt /i condor-6.7.18-winnt50-x86.msi %ARGS%

Each property corresponds to answers supplied in the interactive installer as described above. The following is a brief explanation of each property as it applies to unattended installations:

NEWPOOL = < Y | N >
determines whether the installer will create a new pool with the target machine as the central manager.

sets the name of the pool if a new pool is to be created. Possible values are either the name or the empty string "".

RUNJOBS = < N | A | I | C >
determines when Condor will run jobs. This can be set to:

determines what Condor should do when it has to stop the execution of a user job. When set to Y, Condor will vacate the job and start it somewhere else if possible. When set to N, Condor will merely suspend the job in memory and wait for the machine to become available again.

will cause the installer to configure the machine as a submit node when set to Y.

sets the e-mail address of the Condor admininistrator. Possible values are an e-mail address or the empty string "".

is a list of host names that are allowed to issue READ commands to Condor daemons. This value should be set in accordance with the HOSTALLOW_READ setting in the configuration file, as described in section 3.6.10 on page [*].

is a list of host names that are allowed to issue WRITE commands to Condor daemons. This value should be set in accordance with the HOSTALLOW_WRITE setting in the configuration file, as described in section 3.6.10 on page [*].

is a list of host names that are allowed to issue ADMINISTRATOR commands to Condor daemons. This value should be set in accordance with the HOSTALLOW_ADMINISTRATOR setting in the configuration file, as described in section 3.6.10 on page [*].

defines the path to where Condor will be installed.

should be set to whatever INSTALLDIR is set to, with the additional restriction that it cannot end in a backslash. The installer will be fixed in an upcoming version of Condor to not require this property.

defines the host name of the pool's central manager.

defines the accounting (or UID) domain the target machine will be in.

defines the path to Java virtual machine on the target machine.

defines the host name of the SMTP server that the target machine is to use to send e-mail.

determines whether the Condor service will be started after the installation completes.

After defining each of these properties for the MSI installer, the installer can be started with the msiexec command. The following command starts the installer in unattended mode, and dumps a journal of the installer's progress to a log file:
msiexec /qb /l* condor-install-log.txt /i condor-6.7.18-winnt50-x86.msi [property=value] ...

More information on the features of msiexec can be found at Microsoft's website at Manual Installation Condor on Windows

If you are to install Condor on many different machines, you may wish to use some other mechanism to install Condor on additional machines rather than running the Setup program described above on each machine.

WARNING: This is for advanced users only! All others should use the Setup program described above.

Here is a brief overview of how to install Condor manually without using the provided GUI-based setup program:

The Service
The service that Condor will install is called "Condor". The Startup Type is Automatic. The service should log on as System Account, but do not enable "Allow Service to Interact with Desktop". The program that is run is condor_ master.exe.

The Condor service can be installed and removed using the sc.exe tool, which is included in Windows XP and Windows 2003 Server. The tool is also available as part of the Windows 2000 Resource Kit.

Installation can be done as follows:

sc create Condor binpath= c:\condor\bin\condor_master.exe

To remove the service, use:

sc delete Condor

The Registry
Condor uses a few registry entries in its operation. The key that Condor uses is HKEY_LOCAL_MACHINE/Software/Condor. The values that Condor puts in this registry key serve two purposes.
  1. The values of CONDOR_CONFIG and RELEASE_DIR are used for Condor to start its service.

    CONDOR_CONFIG should point to the condor_config file. In this version of Condor, it must reside on the local disk.

    RELEASE_DIR should point to the directory where Condor is installed. This is typically C:\Condor, and again, this must reside on the local disk.

  2. The other purpose is storing the entries from the last installation so that they can be used for the next one.

The Filesystem
The files that are needed for Condor to operate are identical to the Unix version of Condor, except that executable files end in .exe. For example the on Unix one of the files is condor_master and on Condor the corresponding file is condor_master.exe.

These files currently must reside on the local disk for a variety of reasons. Advanced Windows users might be able to put the files on remote resources. The main concern is twofold. First, the files must be there when the service is started. Second, the files must always be in the same spot (including drive letter), no matter who is logged into the machine.

Note also that when installing manually, you will need to create the directories that Condor will expect to be present given your configuration. This normally is simply a matter of creating the log, spool, and execute directories. Condor Is Installed Under Windows ... Now What?

After the installation of Condor is completed, the Condor service must be started. If you used the GUI-based setup program to install Condor, the Condor service should already be started. If you installed manually, Condor must be started by hand, or you can simply reboot. NOTE: The Condor service will start automatically whenever you reboot your machine.

To start Condor by hand:

  1. From the Start menu, choose Settings.
  2. From the Settings menu, choose Control Panel.
  3. From the Control Panel, choose Services.
  4. From Services, choose Condor, and Start.

Or, alternatively you can enter the following command from a command prompt:

         net start condor

Run the Task Manager (Control-Shift-Escape) to check that Condor services are running. The following tasks should be running:

Also, you should now be able to open up a new cmd (DOS prompt) window, and the Condor bin directory should be in your path, so you can issue the normal Condor commands, such as condor_ q and condor_ status. Condor is Running Under Windows ... Now What?

Once Condor services are running, try building and submitting some test jobs. See the README.TXT file in the examples directory for details.

3.2.7 RPMs

RPMs are available in Version 6.8.7. This packaging method provides for installation and configuration in one easy step. It is currently available for Linux systems only.

The format of the installation command is

  rpm -i <filename> --prefix=<installation dir>

The user provides the path name to the directory used for the installation. The rpm program calls condor_ configure to do portions of the installation. If the condor user is present on the system, the installation script will assume that that is the effective user that Condor should run as (see section 3.6.12 on page [*]). If the condor user is not present, the daemon user will be used. This user will be present on all Linux systems. Note that the user can later be changed by running the condor_ configure program using the owner option, of the format:

  condor_configure  --owner=<user>

After a successful installation, the CONDOR_CONFIG configuration variable must be set to point to

   <installation dir>/etc/condor_config
before starting Condor daemons or invoking Condor tools.

RPM upgrade (-u option) does not currently work for Condor Version 6.8.7.

3.2.8 Upgrading - Installing a Newer Version of Condor

An upgrade changes the running version of Condor from the current installation to a newer version. The safe method to install and start running a newer version of Condor in essence is: shutdown the current installation of Condor, install the newer version, and then restart Condor using the newer version.

To allow for falling back to the current version, place the new version in a separate directory. Copy the existing configuration files, and modify the copy to point to and use the new version. Set the CONDOR_CONFIG environment variable to point to the new copy of the configuration, so the new version of Condor will use the new configuration when restarted.

When upgrading from an earlier version of Condor to a version of 6.8, note that the configuration settings must be modified for security reasons. Specifically, the HOSTALLOW_WRITE configuration variable must be explicitly changed, or no jobs may be submitted, and error messages will be issued by Condor tools.

3.2.9 Installing the CondorView Client Contrib Module

The CondorView Client contrib module is used to automatically generate World Wide Web pages to display usage statistics of a Condor pool. Included in the module is a shell script which invokes the condor_ stats command to retrieve pool usage statistics from the CondorView server, and generate HTML pages from the results. Also included is a Java applet, which graphically visualizes Condor usage information. Users can interact with the applet to customize the visualization and to zoom in to a specific time frame. Figure 3.2 on page [*] is a screen shot of a web page created by CondorView. To get a further feel for what pages generated by CondorView look like, view the statistics for the University of Wisconsin-Madison pool by visiting the URL and clicking on Condor View.

Figure 3.2: Screenshot of CondorView Client

After unpacking and installing the CondorView Client, a script named make_stats can be invoked to create HTML pages displaying Condor usage for the past hour, day, week, or month. By using the Unix cron facility to periodically execute make_stats, Condor pool usage statistics can be kept up to date automatically. This simple model allows the CondorView Client to be easily installed; no Web server CGI interface is needed. Step-by-Step Installation of the CondorView Client

  1. Make certain that the CondorView Server is configured. Section 3.12.5 describes configuration of the server. The server logs information on disk in order to provide a persistent, historical database of pool statistics. The CondorView Client makes queries over the network to this database. The condor_ collector includes this database support. To activate the persistent database logging, add the following entries to the configuration file on the central manager:
        POOL_HISTORY_DIR = /full/path/to/directory/to/store/historical/data 
        KEEP_POOL_HISTORY = True

  2. Create a directory where CondorView is to place the HTML files. This directory should be one published by a web server, so that HTML files which exist in this directory can be accessed using a web browser. This directory is referred to as the VIEWDIR directory.

  3. Download the 6.1.8 view_client contrib module.

  4. Unpack or untar this contrib module into the directory VIEWDIR. This creates several files and subdirectories.

  5. Edit the make_stats script. At the beginning of the file are six parameters to customize. The parameters are

    A brief name that identifies an organization. An example is ``Univ of Wisconsin''. Do not use any slashes in the name or other special regular-expression characters. Avoid the characters $\mathtt{\backslash}$^ and $.

    The e-mail address of the Condor administrator at your site. This e-mail address will appear at the bottom of the web pages.

    The full path name (not a relative path) to the VIEWDIR directory set by installation step 2. It is the directory that contains the make_stats script.

    The full path name of the directory which contains the condor_ stats binary. The condor_ stats program is included in the <release_dir>/bin directory. The value for STATSDIR is added to the PATH parameter by default.

    A list of subdirectories, separated by colons, where the make_stats script can find the awk, bc, sed, date, and condor_ stats programs. If perl is installed, the path should also include the directory where perl is installed. The following default works on most systems:

  6. To create all of the initial HTML files, run
            ./make_stats setup
    Open the file index.html to verify that things look good.

  7. Add the make_stats program to cron. Running make_stats in step 6 created a cronentries file. This cronentries file is ready to be processed by the Unix crontab command. The crontab manual page contains details about the crontab command and the cron daemon. Look at the cronentries file; by default, it will run make_stats hour every 15 minutes, make_stats day once an hour, make_stats week twice per day, and make_stats month once per day. These are reasonable defaults. Add these commands to cron on any system that can access the VIEWDIR and STATSDIR directories, even on a system that does not have Condor installed. The commands do not need to run as root user; in fact, they should probably not run as root. These commands can run as any user that has read/write access to the VIEWDIR directory. To add these commands to cron, run
      crontab cronentries

  8. Point the web browser at the VIEWDIR directory to complete the installation.

3.2.10 Dynamic Deployment

Dynamic deployment is a mechanism that allows rapid, automated installation and start up of Condor resources on a given machine. In this way any machine can be added to a Condor pool. The dynamic deployment tool set also provides tools to remove a machine from the pool, without leaving residual effects on the machine such as leftover installations, log files, and working directories.

Installation and start up is provided by condor_ cold_start. The condor_ cold_start program determines the operating system and architecture of the target machine, and transfers the correct installation package from an ftp, http, or grid ftp site. After transfer, it installs Condor and creates a local working directory for Condor to run in. As a last step, condor_ cold_start begins running Condor in a manner which allows for later easy and reliable shut down.

The program that reliably shuts down and uninstalls a previously dynamically installed Condor instance is condor_ cold_stop. condor_ cold_stop begins by safely and reliably shutting off the running Condor installation. It ensures that Condor has completely shut down before continuing, and optionally ensures that there are no queued jobs at the site. Next, condor_ cold_stop removes and optionally archives the Condor working directories, including the log directory. These archives can be stored to a mounted file system or to a grid ftp site. As a last step, condor_ cold_stop uninstalls the Condor executables and libraries. The end result is that the machine resources are left unchanged after a dynamic deployment of Condor leaves. Configuration and Usage

Dynamic deployment is designed for the expert Condor user and administrator. Tool design choices were made for functionality, not ease-of-use.

Like every installation of Condor, a dynamically deployed installation relies on a configuration. To add a target machine to a previously created Condor pool, the global configuration file for that pool is a good starting point. Modifications to that configuration can be made in a separate, local configuration file used in the dynamic deployment. The global configuration file must be placed on an ftp, http, grid ftp, or file server accessible by condor_ cold_start. The local configuration file is to be on a file system accessible by the target machine. There are some specific configuration variables that may be set for dynamic deployment. A list of executables and directories which must be present for Condor to start on the target machine may be set with the configuration variables DEPLOYMENT_REQUIRED_EXECS and DEPLOYMENT_REQUIRED_DIRS . If defined and the comma-separated list of executables or directories are not present, then condor_ cold_start exits with error. Note this does not affect what is installed, only whether start up is successful.

A list of executables and directories which are recommended to be present for Condor to start on the target machine may be set with the configuration variables DEPLOYMENT_RECOMMENDED_EXECS and DEPLOYMENT_RECOMMENDED_DIRS . If defined and the comma-separated lists of executables or directories are not present, then condor_ cold_start prints a warning message and continues. Here is a portion of the configuration relevant to a dynamic deployment of a Condor submit node:

                               STARTER_STANDARD, SHADOW, SHADOW_PVM, \
                               SHADOW_STANDARD, GRIDMANAGER, GAHP, CONDOR_GAHP

Additionally, the user must specify which Condor services will be started. This is done through the DAEMON_LIST configuration variable. Another excerpt from a dynamic submit node deployment configuration:


Finally, the location of the dynamically installed Condor executables is tricky to set, since the location is unknown before installation. Therefore, the variable DEPLOYMENT_RELEASE_DIR is defined in the environment. It corresponds to the location of the dynamic Condor installation. If, as is often the case, the configuration file specifies the location of Condor executables in relation to the RELEASE_DIR variable, the configuration can be made dynamically deployable by setting RELEASE_DIR to DEPLOYMENT_RELEASE_DIR as


In addition to setting up the configuration, the user must also determine where the installation package will reside. The installation package can be in either tar or gzipped tar form, and may reside on a ftp, http, grid ftp, or file server. Create this installation package by tar'ing up the binaries and libraries needed, and place them on the appropriate server. The binaries can be tar'ed in a flat structure or within bin and sbin. Here is a list of files to give an example structure for a dynamic deployment of the condor_ schedd daemon.

% tar tfz latest-i686-Linux-2.4.21-37.ELsmp.tar.gz

next up previous contents index
Next: 3.3 Configuration Up: 3. Administrators' Manual Previous: 3.1 Introduction   Contents   Index