On Jun 9, 2006, at 6:12 AM, Martin Knoblauch wrote:
> one really should not post tired an sick ... :-( My analysis of the
> problem with hostname mapped to 127.0.02 was incomplete. The resulting
> conclusion was wrong and the posted fix was broken (both times ... :-(
>
> OK, here I go again.
>
> Problem: when the local hostname is mapped to 127.0.0.2, lamboot
> throws
> a "no-localhost" error. This is incorrect. It should either succeed
> (one host in the universe), or throw "resolve-localhost" (unless -l is
> given).
>
> The bug is in "lamnet_findorig". It compares the resolved hosts
> adresses against all network interfaces and bails out if no match is
> found. At least on Linux, it should additionally check whether the
> resolved host address is in network "127". The appended (compiled and
> tested this time) patch implements this. It also modifies the check
> for
> "127.0.0.1" for globus and rsh boot. The patch is against 7.1.2.
Thanks for the patch! It looks ok, and works well on our supported
platforms, so I have committed it to our release branch. It is also
available in the 7.1.3a1 pre-release I posted this afternoon:
http://www.lam-mpi.org/beta/
Thanks again,
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have a LAM/MPI day: http://www.lam-mpi.org/
|
