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
This is with regards to http://www.open-mpi.org/faq/?category=rsh#ssh-keys
It says to check if you have an ssh-agent running. How are you supposed
to do that? I've tried "ps -u myusername | grep ssh-agent", but didn't
know if that's the proper thing to do.
Also, it appears that I do *NOT* h
Chris,
I'm puzzled by the fact that the problem might come from the gfortran compiler.
I use it daily on my MAC, with LAPACK and BLAS, and so far I didn't has any
strange problems. If it can help I use the gfortran precompiler compiler from
MAC HPC (http://hpc.sourceforge.net/).
I might have a
George,
Thank you very much for you well argumented answer. Indeed, I missed
something because I used MPI_Comm_remote_size in my spawned application.
Mathieu
George Bosilca wrote:
Mathieu,
Your MPI_COMM_UNIVERSE is a inter-communicator, and therefore the MPI_Comm_size and MPI_Com
