[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Condor-users] Hard-coded paths in Condor binaries?
- Date: Thu, 15 Nov 2007 18:31:33 +0100
- From: Pascal Jermini <pascal+condor@xxxxxxxxxxxxxxxx>
- Subject: [Condor-users] Hard-coded paths in Condor binaries?
It has been brought to my attention that Condor (on Linux, but this may be
true for other platforms as well) was creating a lot of syslog entries
concerning the /home automount point on a few compute nodes of our pool.
After inspection it turns out that Condor is trying to access a file located
in /home/condor, even when there's no reference to that directory in any
configuration files. This breaks havoc in the logs, since we are getting a
lots of entries in automount's logs concerning this non-existent directory.
I've strace'd the startup of the Condor daemons and I found the following:
O_RDONLY) = -1 ENOENT (No such file or directory)
and by running a crude "strings dir_135656 bin/* sbin/*" in the condor
directory it appears that most (all?) binaries include this string.
Any reason to have this hard-coded path in there? It would be great if this
issue could be resolved in a future version of Condor!