On Mar 4, 2004, at 10:57 PM, Joel Falcou wrote:
> I run into somethign strange. I installed
> LAM using the MAC OS X Binary Package. All is installing fine
> but wheneevr I try to lamboot, it fails on the first hboot command.
> Authentification are working right but it seems it can' found the LAM
> binary on the host machines.
Can you send the output from "lamboot -vv"? Are you trying to run on
one node or multiple nodes? Also, what version of OS X are you using?
> Strangely enough, if I manually run hboot and such on the host,
> they're found
> and executed.
That usually points to a "dot file" problem, although it is possible
there is something else going on. You might want to take a look at the
FAQ on the LAM web site. In the mean time, the output from the lamboot
-vv should help us find the problem.
> I saw that the MAC OS Binary Package set the LAM prefix to be
> /usr/local but the binary are
> effectively installed in /usr/local/bin. Could this be a problem,
> should I create symbolic links from there or is there a way to change
> the prefix ?
This is a bit of packaging nomenclature that is a bit confusing. The
LAM prefix in the binary packages is /usr/local/. That means that
binaries are installed in /usr/local/bin/, libraries are in
/usr/local/lib/, etc. So everything is ok, and definitely no need to
create symbolic links. lamboot uses your PATH to find hboot, and while
/usr/local/bin should be in your path, it is highly unlikely that
/usr/local is in your path (nor should it be).
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have a LAM/MPI day: http://www.lam-mpi.org/
|
