The new Condor installation/configuration script, condor_configure, simplifies the task of installing and re-configuring the Condor software that comes with VDT.
When installing the Condor package as part of VDT
condor_configure will perform the following without asking user
During the VDT install process condor_configure writes important messages to the VDT post-install README file ($VDT_LOCATION/post-install/README). It is a good idea to check it for messages about things that the script was not able to automatically configure, errors it encountered, etc.
After the initial installation the user may always re-run condor_configure from $VDT_LOCATION/condor directory to change certain important options such as setting the central manager, changing the running daemons, etc. In particular:
--make-personal-condorCreates a personal Condor (i.e. a 1-node pool running on local machine).
--type=[submit],[execute],[manager]Determines which role(s) the machine will perform in a pool (which translates to which daemons will run).
--central-manager=hostConnect to a pool with central manager on host
--local-dir=local_dirSets the local directory (Condor home) to the specified directory. Moves the relevant Condor directories (log, spool, execute) there.
--owner=ownerRun Condor daemons as specified user (can be either ID or username). (Only applicable when condor_configure is run by root, otherwise the current user is assumed). Changes ownership of log,spool,execute directories to specified user, and instructs Condor system to run as that user (by setting CONDOR_IDS in the config file).
--verbosePrint detailed information about changes being made to configuration.
With the exception of the initial install the configuration script only makes changes to the local configuration file ($VDT_LOCATION/condor/local.$HOSTNAME/condor_config.local). When it does it backs up the old version of the config file by appeding a timestamp to it.