Hi Pascal, Iâve been using this approach for years â the trick here is to leave the condor_config file exactly as is, and then in the condor_config.local you set the LOCAL_CONFIG_DIR
& LOCAL_CONFIG_FILE parameters to point to the shared config directory, something along these lines: SHARED_CONFIG_DIR = /user/condor LOCAL_CONFIG_FILE = $(SHARED_CONFIG_DIR)/config/host.d/$(HOSTNAME) LOCAL_CONFIG_DIR = $(SHARED_CONFIG_DIR)/config/config.d Regards, -Michael Pelletier. From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx]
On Behalf Of pascal ebay I am reading the doc to set up an installation mixing Windows and Linux nodes. Section 3.14.3 presents a nice way of minimizing duplication of the configuration by hosting it on a shared folder and using $(OPSYS) value in filenames. However in 3.2.3.5, it says: CONDOR_CONFIG should point to the condor_config file. In this version of HTCondor, it must reside on the local disk.
This piece of information seems contradictory with the setup above. So, should condor_config be shared in a network drive for Windows node after all? Thanks Pascal |