Correct, I am using 1.2.6 and not running a persistent deamon (thank you for
the link Pak by the way).
However, in the Client/Server test thread I'm showing a complete example
where I tried to run both applications through the same mpirun command and
still having an internal error:
http://www.open-
Looking at the orignal email, it looks like Alberto might not have the
persistent daemon up since he's using OMPI 1.2,, so he'll need to start
the persistent daemon and establish a universe before the client server
programs can connect (and probably would work for look up as well?!).
These page
I assume you are using some variant of OMPI 1.2?
When last I checked, which admittedly was quite a while ago, this worked on
the 1.2.x series. However, I note something here that may be a problem. In
the 1.2.x series, we do not have a global publish/lookup service - the
application doing the publi
I am having error using MPI_Lookup_name. The same program works fine
when using MPICH:
/usr/local/bin/mpiexec -np 2 ./client myfriend
Processor 0 (662, Sender) initialized
Processor 0 looking for service myfriend-0
Processor 1 (664, Sender) initialized
Processor 1 looking for service myfriend-
Hi,
1)Today I have compiled my first MPI application by using OPEN MPI
compiler mpicc.
A very strange thing happens, a program that worked
correctly with MPICH2 now gives me an error.
I show you the error
message that appears when I execute it:
*** An error occurred in
MPI_Lookup_name
*** on
