On 08/23/2011 12:47 PM, Thomas Moschny wrote:
2011/8/23 Orion Poplawski<orion(a)cora.nwra.com>:
> See https://bugzilla.redhat.com/show_bug.cgi?id=719785
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.
Would something like this work?
eval `/lib64/ld-linux-x86-64.so.2 --library-path ''
/usr/bin/modulecmd bash $*`
(on a 64bit system; on a 32bit system it would need to use /lib/ld-linux.so.2).
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
I'm CC'ing the packaging list to get their thoughts.
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com