Re: [HTCondor-users] config.d vs condor_config.local

["John (TJ) Knoeller" <johnkn@xxxxxxxxxxx>]

I'm puzzled, if condor_config has an explicit value for LOCAL_CONFIG_FILE, then it should be parse before config.d.

could you please post the output to this command so I can understand what's happening here?

   condor_config_val -verbose -dump 'LOCAL_(CONFIG|DIR)'

thanks,
tj

On 8/8/2014 4:31 PM, Dimitri Maziuk wrote:

On 08/08/2014 03:46 PM, John (TJ) Knoeller wrote:

...

I suspect you will see that LOCAL_CONFIG_FILE refers to $(LOCAL_DIR),
but that LOCAL_DIR isn't
set in condor_config, but later - so the local config file can't be
found until after the config directory has been read,
and therefore it is being parsed last.

No, I am not setting anything, you guys are shipping the rpm with
condor_config that says
LOCAL_DIR = /var
LOCAL_CONFIG_FILE = /etc/condor/condor_config.local
LOCAL_CONFIG_DIR = /etc/condor/config.d

You're also including condor_config.local in the rpm. So if I want to
make sure whatever the rpm maintainer put in there does not override my
settings in config.d I just need to add "LOCAL_CONFIG_FILE = /dev/null"
to my config.d. Works for me.

Thanks for the explanation, please consider putting in the manual

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/