From: Brian W. B. <brb...@la...> - 2004-06-10 21:50:43
|
On Jun 10, 2004, at 2:10 PM, Luke Palmer wrote: > The lamboot problem is because the local_bproc_resolve function doesn't > know how to handle localhost. So, I removed it from my bhosts file and > tried it, but encountered another error- > > ----------------------------------------------------------------------- > ------ > The boot SSI bproc module found that your local host is not in the > hostfile "./bhost". > > 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. > > I'm not sure I understand why this is a requirement. It certainly > isn't > with the RSH version of LAM. Can anyone explain? > Actually, the "local host name" not "localhost" must be in your boot schema and has always had to be in your boot schema (even for RSH). The current patch for LAM and bproc-4 support isn't going to work. I need to figure out what the "right" way to identify an IP address as belonging to a master node is and to figure out why bproc_nodeinfo keeps returning -1 on me. I'm kind of hoping one of the LANL guys will just tell me I'm being stupid and correct my evil ways ;). Brian -- Brian Barrett LAM/MPI developer and all around nice guy Have a LAM/MPI day: http://www.lam-mpi.org/ |