I regularly run jobs like that on 1.3.1 - it has no desire to use ssh
to start anything. On a local host such as this command uses, all
mpiexec does is fork/exec the procs.
It sounds like something strange is going on in your environment that
makes OMPI think it is launching on a remote host. Most likely cause
is something in your Ethernet configuration. Can you send us the
output of ifconfig (or whatever your equivalent is)?
On Mar 23, 2009, at 11:23 AM, Olaf Lenz wrote:
> I've tried to find anything on this on the mailings list or anywhere
> else, but I wasn't able to.
> In OpenMPI 1.2.x, I was able to simply run
> mpiexec -n 2 hostname
> on my Dual core machine without any problems. All MPI tasks
> inherited the environment of the calling shell, and no SSH was used
> Now, using OpenMPI 1.3.1, it seems to try to use ssh to start the
> processes, which on the one hand requires me to enter the password/
> passphrase, and furthermore destroys the environment. This make it
> much less convenient to use OpenMPI on Multicore machines, compared
> to 1.2.x.
> What's the reason for this change in behavior? And is there a way to
> get back to the old behavior?
> Best regards
> users mailing list