One further point that I missed in my earlier note: if you are starting the
parent as a singleton, then you are fooling yourself about the "without mpirun"
comment. A singleton immediately starts a local daemon to act as mpirun so that
comm_spawn will work. Otherwise, there is no way to launch
On 6/16/2012 8:03 AM, Roland Schulz wrote:
Hi,
I would like to start a single process without mpirun and then use
MPI_Comm_spawn to start up as many processes as required. I don't want
the parent process to take up any resources, so I tried to disconnect
the inter communicator and then
I'm afraid there is no option to keep the job alive if the parent exits. I
could give you several reasons for that behavior, but the bottom line is that
it can't be changed.
Why don't you have the parent loop across "sleep", waking up periodically to
check for a "we are done" message from a
Hi,
I would like to start a single process without mpirun and then use
MPI_Comm_spawn to start up as many processes as required. I don't want the
parent process to take up any resources, so I tried to disconnect the inter
communicator and then finalize mpi and exit the parent. But as soon as I do
