> <snipped>
>
>BTW, some previous posts suggested setting LAMRSH=ssh, but the LAM 7.0 User
>Guide seem to suggest that LAM would automatically choose between SSH and
>RSH, is that true? So, it would try SSH first, and than RSH? The Guide
>also has this -ssi boot rsh option -- I am running LAM 6.5.9 and this option
>is not available, right?
Actually, the sentence that you are referring to ("Typically, LAM chooses
the right boot module automatically..." on page 21 of the LAM user doc,
right?) implies that LAM automatically chooses the appropriate boot SSI
module from among 'rsh', 'tm', 'bproc', 'condor' and 'globus'. Note that
'rsh' in this context is a generic name that refers to both rsh and ssh
remote-execution agents.
If the 'rsh' boot SSI module is chosen either automatically or because the
-ssi boot rsh option was specified, this module determines whether to use
rsh or ssh based upon the following things (in order):
1) the value specified with the 'rsh_boot_agent' SSI parameter (refer to
Section 8.1.7 in the LAM user doc).
2) value of the LAMRSH env variable.
3) compiled default (specified with the --with-rsh option to configure).
And yes, the SSI framework is a new addition in LAM 7.0. So the -ssi
options do not exist in earlier releases of LAM.
--
Sriram Sankaran
email: ssankara_at_[hidden]
http://www.lam-mpi.org/
|
