[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Problem with config



On 09/20/2011 04:28 AM, Lukas Slebodnik wrote:
On Tue, Sep 20, 2011 at 11:37:20AM +0800, Jeff Zhao wrote:
refer this article:
http://spinningmatt.wordpress.com/2011/06/12/getting-started-creating-a-multiple-node-condor-pool/,
I do it as following,

[root@node1 ~]# cat>  /etc/condor/config.d/exec.config
CONDOR_HOST = 192.168.20.24
DAEMON_LIST = MASTER, STARTD
ALLOW_WRITE = $(ALLOW_WRITE), $(CONDOR_HOST)
^D

but I found

# condor_config_val -config
Configuration source:
         /etc/condor/condor_config
Local configuration sources:
         /etc/condor/config.d/exec.config
         /etc/condor/condor_config.local

#condor_config_val -v daemon_list
DAEMON_LIST: COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD
   Defined in '/etc/condor/condor_config.local', line 33.

# condor_version

$CondorVersion: 7.6.3 Aug 24 2011 BuildID: 362955 $
$CondorPlatform: x86_64_deb_5.0 $

Because the version of the condor or the other reason?

THANKS!

Jeff

Files in LOCAL_CONFIG_DIR ("/etc/condor/config.d/") are processed before
any files listed in LOCAL_CONFIG_FILE ("/etc/condor/condor_config.local").
Order of processing configuration files is listed in output of command
"condor_config_val -config".

You have pasted output of command "condor_config_val -v daemon_list", where you
can see that DAEMON_LIST was last defined in /etc/condor/condor_config.local at
line 33. This is a reason why DAEMON_LIST variable has wrong value.

One of possible solution is to comment redefinition of DAEMON_LIST in file
/etc/condor/condor_config.local

Regards,
Lukas

Or, even better, stop using LOCAL_CONFIG_FILE -

http://spinningmatt.wordpress.com/2011/06/16/customizing-condor-configuration-local_config_fil-vs-local_config_dir/

The Fedora and RHEL packages (I think the UW RHEL package too) use LOCAL_CONFIG_DIR. Other sources (UW tarball, Ubuntu, ?Debian?) may still be using LOCAL_CONFIG_FILE.

Best,


matt