Bug 4513 - LD_LIBRARY_PATH should not be set if no library_path is specified
: LD_LIBRARY_PATH should not be set if no library_path is specified
Status: RESOLVED FIXED
: GRAM
wsrf scheduler interface
: 4.0.2
: PC Linux
: P3 normal
: 4.2.2
Assigned To:
:
: 4.0.x, usability
:
:
  Show dependency treegraph
 
Reported: 2006-06-14 13:09 by
Modified: 2008-10-30 09:11 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2006-06-14 13:09:24
The PBS adapter module is setting LD_LIBRARY_PATH and it's cousin library env
vars to nothing (i.e. "LD_LIBRARY_PATH=;") if no libraryPath elements were
specified in the job description. This is causing problems with the SoftEnv
extensions because it overrides any values SoftEnv would have set for these env
vars.

I propose that these library vars should simply not be set if there are no
occurances of the libraryPath elements in the job description. That would still
allow the user to override SoftEnv with explicity library paths if so desired.
Fixes should be added to HEAD, globus_4_0_branch, and globus_4_0_community.
------- Comment #1 From 2006-06-14 14:29:46 -------
What are the semantics supposed to be for the various ways one can set the
library-path: environment, libraryPath, and softEnv? What should be done if
more than one is present (override, append) and in what order ought they be
evaluated?
------- Comment #2 From 2006-06-14 16:07:18 -------
I would say the order of priority would be SoftEnv, environment, libraryPath
since it goes from least explicit to most explicit. Nothing needs to be done to
check SoftEnv since it doesn't actually set anything explicitly in the adapter
module.
------- Comment #3 From 2008-10-30 09:11:01 -------
committed a fix to the pbs job manager in 4.0 branch, 4.2 branch and trunk