Done - will be in nightly 1.8.2 tarball generated later today.
On May 16, 2014, at 2:57 AM, Siegmar Gross <siegmar.gr...@informatik.hs-fulda.de> wrote: > Hi, > >> This bug should be fixed in tonight's tarball, BTW. > ... >>> It is an unrelated bug introduced by a different commit - >>> causing mpirun to segfault upon termination. The fact that >>> you got the hostname to run indicates that this original >>> fix works, so at least we know the connection logic is now okay. > > tyr fd1026 107 ompi_info | grep "MPI:" > Open MPI: 1.9a1r31784 > tyr fd1026 108 mpiexec -np 3 --host tyr,sunpc1,linpc1 hostname > tyr.informatik.hs-fulda.de > linpc1 > sunpc1 > tyr fd1026 109 > > Perfect! Thank you very much for your help. Tonight the current > version will be mirrored to my other machines, so that I can do > some more tests next week. > > > tyr fd1026 103 ompi_info | grep "MPI:" > Open MPI: 1.8.2a1r31785 > tyr fd1026 104 mpiexec -np 3 --host tyr,sunpc1,linpc1 hostname > [tyr.informatik.hs-fulda.de:21100] [[62538,0],0] CONNECTION > REQUEST ON UNKNOWN INTERFACE > [tyr.informatik.hs-fulda.de:21100] [[62538,0],0] CONNECTION > REQUEST ON UNKNOWN INTERFACE > ^CKilled by signal 2. > Killed by signal 2. > tyr fd1026 105 > > Can you fix the connection logic for 1.8.2 as well? Thank you > very much for your help in advance. > > > Kind regards > > Siegmar > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
