Re: [OMPI devel] MPI_Comm_connect/accept does not work as it should

Okay, yeah - that's a known problem that has previously been discussed on the user list. Still hasn't been fixed, though it is on the short list for repair (probably in the 1.7 series). See bug tracker here: https://svn.open-mpi.org/trac/ompi/ticket/2904 On Sep 12, 2012, at 10:12 AM, Suraj

Re: [OMPI devel] MPI_Comm_connect/accept does not work as it should

I am referring to v1.6. On Sep 12, 2012, at 5:27 PM, Ralph Castain wrote: > what version of ompi are you referring to? > > On Sep 12, 2012, at 8:13 AM, Suraj Prabhakaran > wrote: > >> Dear all, >> >> I observed a strange behavior with MPI_Comm_connect and

Re: [OMPI devel] MPI_Comm_connect/accept does not work as it should

what version of ompi are you referring to? On Sep 12, 2012, at 8:13 AM, Suraj Prabhakaran wrote: > Dear all, > > I observed a strange behavior with MPI_Comm_connect and MPI_Comm_disconnect. > In short, after two processes connect to each other with a port and

[OMPI devel] MPI_Comm_connect/accept does not work as it should

Dear all, I observed a strange behavior with MPI_Comm_connect and MPI_Comm_disconnect. In short, after two processes connect to each other with a port and merge to create a intra comm (rank 0 and rank 1), only one of them (the root) is thereafter able to reach a third new process through

Re: [OMPI devel] MPI_Comm_connect/Accept

Still no luck here, I launch those three processes : term1$ ompi-server -d --report-uri URIFILE term2$ mpirun -mca routed unity -ompi-server file:URIFILE -np 1 simple_accept term3$ mpirun -mca routed unity -ompi-server file:URIFILE -np 1 simple_connect The output of ompi-server shows a

Re: [OMPI devel] MPI_Comm_connect/Accept

Okay, I have a partial fix in there now. You'll have to use -mca routed unity as I still need to fix it for routed tree. Couple of things: 1. I fixed the --debug flag so it automatically turns on the debug output from the data server code itself. Now ompi-server will tell you when it is

Re: [OMPI devel] MPI_Comm_connect/Accept

Well, something got borked in here - will have to fix it, so this will probably not get done until next week. On 4/4/08 12:26 PM, "Ralph H Castain" wrote: > Yeah, you didn't specify the file correctly...plus I found a bug in the code > when I looked (out-of-date a little in

Re: [OMPI devel] MPI_Comm_connect/Accept

Ralph, I've not been very successful at using ompi-server. I tried this : xterm1$ ompi-server --debug-devel -d --report-uri test [grosse-pomme.local:01097] proc_info: hnp_uri NULL daemon uri NULL [grosse-pomme.local:01097] [[34900,0],0] ompi-server: up and running! xterm2$ mpirun

Re: [OMPI devel] MPI_Comm_connect/Accept

Take a gander at ompi/tools/ompi-server - I believe I put a man page in there. You might just try "man ompi-server" and see if it shows up. Holler if you have a question - not sure I documented it very thoroughly at the time. On 4/3/08 3:10 PM, "Aurélien Bouteiller"

Re: [OMPI devel] MPI_Comm_connect/Accept

Ralph, I am using trunk. Is there a documentation for ompi-server ? Sounds exactly like what I need to fix point 1. Aurelien Le 3 avr. 08 à 17:06, Ralph Castain a écrit : I guess I'll have to ask the basic question: what version are you using? If you are talking about the trunk, there

Re: [OMPI devel] MPI_Comm_connect/Accept

I guess I'll have to ask the basic question: what version are you using? If you are talking about the trunk, there no longer is a "universe" concept anywhere in the code. Two mpiruns can connect/accept to each other as long as they can make contact. To facilitate that, we created an "ompi-server"

[OMPI devel] MPI_Comm_connect/Accept

Hi everyone, I'm trying to figure out how complete is the implementation of Comm_connect/Accept. I found two problematic cases. 1) Two different programs are started in two different mpirun. One makes accept, the second one use connect. I would not expect MPI_Publish_name/Lookup_name to