My apologies - Prakash and I solved this off-list. I should have posted the
final solution here too so any interested parties would know the answer.
The problem actually is a bug that broke comm_spawn in 1.2.2 and may well be
present in the entire 1.2 code series (I have not checked the prior
sub-releases). I provided a patch to Prakash that solves the problem, and
have requested that a slightly different version be released as part of
Sorry for forgetting to post this back to the list. Anyone needing the patch
for 1.2.2 prior to the next sub-release should just let me know and I'll
On 6/8/07 12:39 PM, "Jeff Squyres" <jsquyres_at_[hidden]> wrote:
> On Jun 5, 2007, at 10:27 AM, Prakash Velayutham wrote:
>> I know. I could not start another client code before this. So just
>> wanted to check if /bin/hostname works with the spawn.
> It will not. MPI_COMM_SPAWN assumes that you are spawning an MPI
> application and therefore after the process is launched, it tries to
> do MPI-level coordination with it to setup new communicators, etc.
> FWIW: MPI-2 says that you are *only* allowed to launch MPI processes
> through MPI_COMM_SPAWN[_MULTIPLE].
> This could well be the error that you are seeing (I haven't tried it
> myself to see what would happen).