On May 19, 2009, at 8:29 AM, Jeff Squyres wrote:
> fork() support in OpenFabrics has always been dicey -- it can lead
> to random behavior like this. Supposedly it works in a specific set
> of circumstances, but I don't have a recent enough kernel on my
> machines to test.
> It's best not to use calls to system() if they can be avoided.
> Indeed, Open MPI v1.3.x will warn you if you create a child process
> after MPI_INIT when using OpenFabrics networks.
The MPI code isn't calling fork or system. The serial code is calling
system("mpirun cp2k.popt"). That runs to completion, processes the
output files, and calls system("mpirun cp2k.popt") again, and so on.
Is that in fact likely to be a problem?