Greetings, and thanks for your report! Is there a valid way lam could work around this /etc/hosts breakage? The report in 316099 appears to indicate that the problem has been resolved by never associating 127.0.0.1 with the canonical name of the local host. Does this solve the issue?
Take care, Sergio Gelato <[email protected]> writes: > Package: lam-runtime > Version: 7.1.2-2 > > By default, the Debian installer sets up an entry in /etc/hosts mapping the > local host's name to the IP address 127.0.1.1. See Debian bug #316099. > > This causes lamboot to fail with the following message when the hostfile > contains the name of the local host: > > The boot SSI rsh module found that your local host is not in the > hostfile "hostfile". > > The local host name *must* be in the list of hosts in the hostfile. > In other words, you must boot LAM from a node that will be part of the > universe. > > Commenting out the 127.0.1.1 line in /etc/hosts makes the problem disappear, > as does replacing 127.0.1.1 with the external IP address of the local host. > > > > > > -- Camm Maguire [email protected] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
