Re: [Condor-users] Stork not setting LD_LIBRARY_PATH defined in STORK_ENVIRONMENT

[Jeff Weber <weber@xxxxxxxxxxx>]

Emir:

Neither Condor nor Stork explicity remove LD_LIBRARY_PATH from the
environment.  I did some checks with test files like yours, and indeed
LD_LIBRARY_PATH appears in the executed module environment.  This occurs
when inheriting the environment from shell (and condor_master), and when
setting the environment via STORK_ENVIRONMENT.  I was running Stork from
the user level, not root.

We strongly recommend running Stork at the user level.  What is your
config, including operating system?  Are you running Stork as root or
setuid?  Linux may remove LD_LIBRARY_PATH when running setuid.

	Jeff

On Thu, 2005-09-15 at 13:15 +0200, Emir Imamagic wrote:
> Hi,
> 
> I'm using Condor 6.7.10 and latest Stork contib modules. Globus 
> installation is in a non-standard directory /home/globus/globus, so I 
> added environment variables in STORK_ENVIRONMENT:
> 
> STORK_ENVIRONMENT = 
> PATH=/home/globus/globus/bin;LD_LIBRARY_PATH=/home/globus/globus/lib
> 
> However, Condor doesn't set the LD_LIBRARY_PATH value. Every stork job 
> fails with error:
> "GLOBUS error: globus-url-copy: error while loading shared libraries: 
> libglobus_gass_copy_gcc32.so.0: cannot open shared object file: No such 
> file or directory\n"

-- 
Jeff Weber
Research Staff, Condor Project
Dept. of Computer Sciences
University of Wisconsin, USA
http://www.cs.wisc.edu/condor/