Not quite. Just the head node needs to have its public key in the
authorized_keys file of each slave. The head node opens up a ssh tunnel to
each slave machine in order to boot LAM and run programs. Once the tunnel
is open, that's it. You're off and running like you were with rsh.
Damien
----- Original Message -----
From: "Stubby Cat" <lam32767_at_[hidden]>
To: <lam_at_[hidden]>
Sent: Saturday, March 13, 2004 2:07 PM
Subject: LAM: Moving from rsh to ssh
> By simply putting a hosts.equiv out there, with all my boxes listed, I am
automatically able to log in from any box to any box.
>
> Looking at the various logs, and doing lamboot -d to see all the messages,
implies that every box needs to log on to every box.
>
> Now that I am trying to make the whole thing work using ssh instead of
rsh, I do wonder if I will need to make every box's public key appear in
every other box's authorized_keys file.
>
> OR - do I get by just having every non-head node only authorized on the
head node?
>
> I read through the manual, and there was no explicit mention on this
subject.
>
>
>
> ____________________________________________________________
> Find what you are looking for with the Lycos Yellow Pages
>
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
