On Tue, 15 Jul 2003, Michael Lees wrote:
> > You might want to check your "dot" files (similar to what is shown below,
> > or perhaps just "ssh othernode env | grep LD_") and ensure that your
> > LD_LIBRARY_PATH is set properly on the remote nodes.
>
> Bingo!
>
> I checked the ssh documentation and there is a file
> $HOME/.ssh/environment which adds lines of the format 'VARNAME=value' So
> I added an environment file and added the line..
>
> LD_LIBRARY_PATH=/usr/local/lib:
>
> rebooted 'lamboot mynodes' and hey presto is works.
I'm a little surprised that the C++ libraries aren't found automatically,
but if this makes it work -- great. :-)
> Thanks for your help guys, out of curiousity is this mentioned in the
> installation guide?
No. Technically it's outside the scope of LAM -- if you can't run C++
programs on a remote node, it's a problem with your environment that you
need to fix. But in a practical sense, it still falls under the user
perception of "hey, my LAM is broken" category, even though it's not LAM's
fault :-). We Llamas go back and forth about this (i.e., whether to
include such details in LAM documentation), and usually err on the side of
"search the mailing lists" rather than try to reproduce ssh documentation
in LAM documentation (particularly because there's multiple
implementations and versions of SSH, and they work differently, etc.).
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
