Using a Preexisting Condor Installation
Applicable only to VDT 1.2.0 or later
If you are installing the VDT server and you have an external
Condor installation that you would like to use in place of the Condor
that is installed with VDT you can specify it by setting
two environment variables described below before installing the VDT.
Doing so will produce the following effects:
- Condor will NOT be installed as part of VDT
- $VDT_LOCATIONsetup.[c]sh will set PATH, MANPATH, CONDOR_LOCATION,
CONDOR_CONFIG to point to the necessary locations in your external Condor
- Globus gatekeeper (/etc/xinetd.d/globus-gatekeeper) and Globus condor jobmanager ($VDT_LOCATION/globus/lib/perl/Globus/GRAM/JobManager/condor.pm) will be set up to submit jobs to your external Condor
- Globus MDS reporter configuration ($VDT_LOCATION/globus/etc/grid-info-resource-ldif.conf) will be setup to report information about the external Condor.
To specify an external Condor installation you need to set the following two environment variables before installing the VDT:
- VDTSETUP_CONDOR_LOCATION - the location of your Condor installation
(e.g. /opt/condor). The Condor bin/, sbin/, etc/, lib/...
directories should be directly under this location.
- VDTSETUP_CONDOR_CONFIG (optional): The location of your Condor configuration
file (if non-standard). Default is $VDTSETUP_CONDOR_LOCATION/etc/condor_config.
For example, if you are using a C shell variant and Condor is
installed in /usr/local/condor and the condor_config file is in
/usr/local/etc you could do:
setenv VDTSETUP_CONDOR_LOCATION /usr/local/condor
setenv VDTSETUP_CONDOR_CONFIG /usr/local/etc/condor_config
pacman -get VDT