The correct way of calling MPI_COMM_SPAWN is to create an MPI_INFO object with they key wdir set to the working directory you want to use for the spawned processes. The working directory for the parent process is not necessarily used for the spawned children. Alternatively, you can just use the full path and you don't need to worry about the working directory unless you have other parts of your application which use it (reading files, etc.). Wesley P.S. We no longer call the project MPICH2. It's just MPICH now as of version 3.x On Jul 1, 2013, at 8:19 AM, Anne-Sophie Mouronval <[email protected]> wrote:
Hi,
I've just installed Mpich2 (using 3.0.4 sources) on my computer and every thing works fine.
Now, I have to work on MPI_Comm_spawn and I have some difficulties.
I've found a nice example that is provided with Mpich2 sources in Mpich2/share/examples/logging This example is based on 2 files : comm2_spawn_parent.c and comm2_spawn_child.c.
I've compiled these two files but I have an error when I try to run this test :
$ mpiexec -np 2 ./comm2_spawn_parent [proxy:1:0@bambou] HYDU_create_process (./utils/launch/launch.c:75): execvp error on file comm2_spawn_child (No such file or directory)
However, "comm2_spawn_child" is present in the current directory.
Thus I've tried to use a "-path" option but it's not recognized : $mpiexec -path mypath -np 2 ./comm2_spawn_parent match_arg (./utils/args/args.c:160): unrecognized argument path
I've looked for some documentation of this test but I haven't found anything.
Regards, Anne-Sophie _______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss