Bogdan Costescu wrote:
>On Mon, 10 Jul 2006, Dennis van Dok wrote:
>
>
>
>>Is it possible to have LD_LIBRARY_PATH set up for each instance of
>>lamd on my nodes? That way, if a process is started by lamd, and by
>>inheritence of the environment,
>>
>>
>
>You have the right idea, but you forget some details :-)
>
>
>[...]
>
>However, setting it up for lamd requires the environment to be set
>into one of the shell start-up file, like the ones you mentioned. This
>is because a remote lamd is started[1] via a simple remote shell;
>there is no mechanism to set environment variables on the remote nodes
>before running lamd, so they have to be set in the shell start-up
>file(s).
>
>
OK, point taken. The issue I'm really having is this: I have a cluster
supporting more than one version of MPI. Ideally, each version lives in
its own space, so I have /opt/lam-6.x.x, /opt/lam-7.x.x, /opt/mpich-x.x,
etc. Now if a scheduler likes to run a six-node lam-7.1.2 job, it would
issue /opt/lam-7.1.2/bin/lamboot with the right parameters, and on each
of the six nodes /opt/lam-7.1.2/bin/lamd would be started (through ssh,
I suppose). Now lamd is linked with /opt/lam-7.1.2/lib/liblam.so.0,
which it can find on merit of its RPATH, but ideally it should think:
hey, I was compiled with --prefix=/opt/lam-7.1.2, let's add
/opt/lam-7.1.2/lib to my LD_LIBRARY_PATH environment!
Your dirty trick comes a long way, I suppose, and I may use that right
now (thank you!) but a cleaner solution would be to patch lamd. You can
see why the /etc/profile.d/ scripts are right out.
Thank you,
Dennis van Dok
--
D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.vl-e.nl
|
