Re: How to ignore LD_LIBRARY_PATH

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On 08/23/2011 12:47 PM, Thomas Moschny wrote:
> 2011/8/23 Orion Poplawski<orion@xxxxxxxxxxxxx>:
>> See for the motivation
>> The environment module system allows users to modify their environment in a
>> predictable way, including setting LD_LIBRARY_PATH.  However, this makes it
>> possible to break the modulecmd binary by putting an incompatible TCL (or
>> other) library earlier in the path.  It would be great if modulecmd were made
>> impervious to such things, but I don't know the best or acceptable method to
>> do this.  I'm guessing using rpaths would be the easiest.
>> Thoughts/suggestions?
> Would something like this work?
> module ()
> {
>      eval `/lib64/ --library-path ''
> /usr/bin/modulecmd bash $*`
> }
> (on a 64bit system; on a 32bit system it would need to use /lib/
> - Thomas

Hmm, I like this idea.  I think it would protect the default system, but still 
allow for end users to override it for some reason.  It might even be 
acceptable upstream.

I'm CC'ing the packaging list to get their thoughts.

Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA/CoRA Division                    FAX: 303-415-9702
3380 Mitchell Lane                  orion@xxxxxxxxxxxxx
Boulder, CO 80301    
packaging mailing list

[Home]     [Fedora Legacy]     [Fedora Desktop]     [Red Hat 9 Bible]     [Fedora Bible]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

Powered by Linux