MPI_Comm_create shouldn't have any effect on existing fd's. Have you run your code through a memory-checking debugger such as valgrind?
On Apr 28, 2011, at 12:57 AM, Randolph Pullen wrote: > I have a problem with MPI_Comm_create, > > My server application has 2 processes per node, 1 listener and 1 worker. > > Each listener monitors a specified port for incoming TCP connections with the > goal that on receipt of a request it will distribute it over the workers in a > SIMD fashion. > > This all works fine unless MPI_Comm_create is called on the listener process. > Then after the call the incoming socket cannot be reached by the external > client processes. The client reports “”Could’t open socket”. No other error > is apparent. I have tried using a variety of different sockets but to no > effect. > > I use OpenMPI 1.4.1 on FD10 with vanilla TCP. The install is totally > standard with no changes. > > Is this a known issue? > > An help appreciated. > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
