I took a few of the points from this thread and updated the rsh faq entry (I
almost fell out of my chair when I saw "lamboot" and "recon" still listed in
that entry -- yoinks!). More updates would be greatly appreciated; could you
send a diff against:
http://svn.open-mpi.org/svn/ompi-www/t
Mark Hahn wrote:
This is with regards to
http://www.open-mpi.org/faq/?category=rsh#ssh-keys
this page is not wonderful.
Hmm, okay, so a non-technical question here: Would you be willing to
rewrite it? It has to pass the dummy test, though.
I make two offers:
1) I'm willing to put bac
Okay, yes, setting SSH_AUTH_SOCK is the right thing to do, but this strikes
me as clumsy.
normally, you should run ssh-agent only on the machine where you sit.
it operates until you logout (you can also tell it to discard keys).
ssh-agent is normally part if your X startup sequence, so that al
Hi,
Am 20.02.2010 um 00:11 schrieb Eugene Loh:
Okay, yes, setting SSH_AUTH_SOCK is the right thing to do, but this
strikes me as clumsy. I'm trying to understand how things should
be set up so that I don't have to take special action each time I
log in. Do I do some .login/.logout magic?
Okay, yes, setting SSH_AUTH_SOCK is the right thing to do, but this
strikes me as clumsy. I'm trying to understand how things should be set
up so that I don't have to take special action each time I log in. Do I
do some .login/.logout magic?
Or, why not just go without a DSA passphrase? The
After you start up ssh-agent once, check env for
SSH_AUTH_SOCK
If you start a new session and the old ssh-agent is still running,
try setting SSH_AUTH_SOCK.
I think there are more refined utilities out there to handle this
situation...
Kenneth
On Fri, 19 Feb 2010, Eugene Loh wrote:
Date: Fr
