4.3. Condor Configuration Mechanics

With the Condor Roll > 8.2.1, Rocks has adopted Condor's configuration directory approach. Configuration files are read in lexicographic order. If a Condor configuration variable is defined multiple times (and/or in multiples files), the last one read is the value of the configuration variable. One can dump all of the current configuration values on a running Condor pool using the command. condor_config_val --dump. The configuration directory itself, is located in /opt/condor/etc/config.d. Within that directory, Rocks creates two configuration files

Most of the configuration values are written to the file 000Rocks.conf. However, the file 99Rocks.conf, can have values written that will overwrite a configuration parameter set by some other means (e.g. by Rocks or by some package that drops a configuration file into the configuration directory). To overwrite a value (say UID_DOMAIN), add an attribute to the Rocks database prefaced by Condor_99Rocks_ so that the full name of the UID_DOMAIN attribute in the database would be Condor_99Rocks_UID_DOMAIN.