as I said LOCAL_CONFIG_FILE is read after the config dir if the
value of LOCAL_CONFIG_FILE has changed. |
If you will just run the command I asked and show the results, then I can probably explain what is happening.
On 8/8/2014 4:51 PM, Dimitri Maziuk wrote:
On second thought,condor_config.local has always been read both before AND AFTER the config directory. It is read after the config directory when LOCAL_CONFIG_FILE resolves to something different after the config directory has been parsed.this is what I see on a node just updated to 8.2.2: If add "myFOO = FALSE" to the rpm-installed /etc/condor/condor_config.local and put "COLLECTOR_NAME = BioMagResBank, UW-Madison" in /etc/condor/config.d/10_pool.conf # condor_config_val -dump | grep -E '(COLLECTOR_NAME|myFOO)' COLLECTOR_NAME = Personal Condor at $(FULL_HOSTNAME) myFOO = FALSE --------------- If I now add "LOCAL_CONFIG_FILE = /dev/null" to /etc/condor/config.d/10_pool.conf, do a full restart (not a _reconfig) # condor_config_val -dump | grep -E '(COLLECTOR_NAME|myFOO)' COLLECTOR_NAME = BioMagResBank, UW-Madison --------------- So if it's read before and after, why is myFOO gone?