LAM: LD_LIBRARY_PATH for lamd

Hi Dennis,

>>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,
>>>      
>>>
I'm neither ssh nor NFS expert, but I have used sometimes
the 
~/.ssh/environment facility (man ssh, sections
"environment" and 
"files", near the end)

If your user's homes are shared along the cluster (and you
don't have 
the 30s NFS update problem , perhaps
they (or the script launching 
lamboot) can create/edit the environment file, adding the
desired 
LD_LIBRARY_PATH value. I have used that facility to export
DISPLAY 
values to lamds-- the same value to all nodes, of course. It
failed 
(very) occassionally, and I thought it could be due to the
30s NFS 
update policy.

> 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).

I think the idea could be creating ~/.ssh/environment right
before 
lamboot... and perhaps waiting 30s or reading man pages for
sync and NFS 
,
before launching lamboot. Isn't it?

> Now lamd is linked with /opt/lam-7.1.2/lib/liblam.so.0,
which it can 
> find on merit of its RPATH, 

Hmm, I wish I knew about linking like Jeff and you do...
I'm still 
re-reading your previous dialogue 

Hope it helps. This is also for the Rmpi software?

-javier
_______________________________________________
This list is archived at http://www.l
am-mpi.org/MailArchives/lam/