The conf.lam file which should be in $LAMHOME/boot is missing. This is usually installed as part of the (IMO bassackwards) lam build/install process. [alazur@nelson alazur]$ export LAMHOME=/usr [alazur@nelson alazur]$ cat bhost nelson [alazur@nelson alazur]$ vi bhost [alazur@nelson alazur]$ export LAMHOME=/usr [alazur@nelson alazur]$ cat bhost localhost [alazur@nelson alazur]$ lamboot ~/bhost LAM 6.3.1/MPI 2 C++/ROMIO - University of Notre Dame hboot: cannot find process schema conf.lam: No such file or directory ----------------------------------------------------------------------------- LAM failed to fork/exec a process to launch the local LAM daemon (lamd). LAM first launches hboot to launch the local LAM daemon, so several things could have gone wrong: - "hboot" itself could not be found (check your $PATH) - "hboot" failed for some reason (consult previous error messages, if any) - Too many processes exist and Unix could not fork another ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- lamboot encountered some error (see above) during the boot process, and will now attempt to kill all nodes that it was previously able to boot (if any). Please wait for LAM to finish; if you interrupt this process, you may have LAM daemons still running on remote nodes. -----------------------------------------------------------------------------
It's included now... but no need to report it doesn't work, I know. I need to fix this badly written software soonish - their buildsystem is hopeless and buggy.