How to set your PATH for LAM is in the FAQ here:
http://www.lam-mpi.org/faq/category4.php3#question8
Doing "rsh node00 env" will tell you what LAM will see for it's PATH, etc.
If you do "rlogin node000" and then do env, it WILL be different.
The difference is caused by the distinction between interactive logins
and non-interactive logins. For unix shells they will source a
different set of dot files to set up the environment. The PATH must
be set properly for BOTH interactive and non-interactive shells.
If there would be some option when building lam to hard code the
paths of the exceutables, and to use full pathnames when doing
the boot ssi modules, this very common problem for new LAM users
could be avoided. This might also avoid the problem of mixed versions
of LAM installed getting confused (and possibly mixed with MPICH parts
too). Consider this a RFE for the LAM >= v7.1
--
Tim Mattox - tmattox_at_[hidden] - http://homepage.mac.com/tmattox/
http://aggregate.org/KAOS/ - http://advogato.org/person/tmattox/
|
