Hui, Thanks for the reply. I am spawning the new process using MPI_COMM_SELF instead of MPI_COMM_WORLD. Maybe that is my problem! Thanks, Kurt From: Zhou, Hui <[email protected]> Sent: Wednesday, December 4, 2019 1:43 PM To: [email protected] Cc: Mccall, Kurt E. (MSFC-EV41) <[email protected]> Subject: [EXTERNAL] Re: [mpich-discuss] What is the best way to connect to a spawned process? Hi Kurt, Let’s say you have a communicator of 10 processes (MPI_COMM_WORLD or any derivatives), and if you use that communicator to spawn process P, the result inter-communicator will be between your original comm (10 processes) and P’s MPI_COMM_WORLD (1 process), right? All original 10 processes should be already connected to P. Did I miss anything? — Hui Zhou On Dec 4, 2019, at 1:31 PM, Mccall, Kurt E. (MSFC-EV41) via discuss <[email protected]<mailto:[email protected]>> wrote: Hi, My job creates 10 processes, and the rank 0 one spawns a distinct process P to function as a master. I’d like to share P’s inter-communicator with the other 9 processes, but it seems that I can’t pass it directly to them through function arguments to those processes (very weird errors happen involving the inter-communicator). What is an efficient way to connect all 10 processes to P? I’ve looked into MPI_Open_port / MPI_Comm_accept / MPI_Comm_connect, but was wondering if there is more streamlined way. (I can’t make rank 0 become the master directly, due to the peculiarities of my PBS/Torque node allocations). Thanks, Kurt _______________________________________________ discuss mailing list [email protected]<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.mpich.org_mailman_listinfo_discuss&d=DwMGaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=6cP1IfXu3IZOHSDh_vBqciYiIh4uuVgs1MSi5K7l5fQ&m=g2p1EF4h4bc33KuF69YHnBiaGoVsBVCakpvpuyd17Bc&s=X6DGY5_SODhWXSV-JOBftbQRvVP40YPeg1zl68Jqt4I&e=>