Re: [Condor-users] Hard-coded paths in Condor binaries?

[Stuart Anderson <anderson@xxxxxxxxxxxxxxxx>]

I have not actually tried, this but there is a utility (at least for Linux)
called chrpath that will change the rpath of compiled programs which I believe
is what you are seeing.

On Thu, Nov 15, 2007 at 11:41:41AM -0600, Steven Timm wrote:
> 
> 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.
> 
> Steve Timm
> 
> ----- 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?
> To: condor-users@xxxxxxxxxxx
> 
> 
> > 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:
> > 
> > open
> > ("/home/condor/execute/dir_13565/userdir/externals/install/globus-4.0.5/cert.pem",
> > 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!
> > 
> > best wishes,
> > 
> > Pascal
> > _______________________________________________
> > Condor-users mailing list
> > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx 
> > with a
> > subject: Unsubscribe
> > You can also unsubscribe by visiting
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> > 
> > The archives can be found at: 
> > https://lists.cs.wisc.edu/archive/condor-users/
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 
> The archives can be found at: 
> https://lists.cs.wisc.edu/archive/condor-users/

-- 
Stuart Anderson  anderson@xxxxxxxxxxxxxxxx
http://www.ligo.caltech.edu/~anderson