[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Hard-coded paths in Condor binaries?
- Date: Thu, 15 Nov 2007 11:41:41 -0600
- From: Steven Timm <timm@xxxxxxxx>
- Subject: Re: [Condor-users] Hard-coded paths in Condor binaries?
Yes--I have seen this many times and reported this almost a year ago. the
developers have told me it's a relic of the NMI build system hardcoding
the library paths into the executable--a relic which IMO needs to get fixed.
I finally gave in and created a special /home/condor automount to
make the errors go away, but there are several other software packages
built via NMI that also have this problem and have not only /home/condor
but various of the developers home directories wired in.
----- Original Message -----
From: Pascal Jermini <pascal+condor@xxxxxxxxxxxxxxxx>
Date: Thursday, November 15, 2007 11:34 am
Subject: [Condor-users] Hard-coded paths in Condor binaries?
> Hello all!
> 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
> issue could be resolved in a future version of Condor!
> best wishes,
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx
> with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at: