Capturing return values from concurrent mpiexecs

[Martin Schafföner]

On Tuesday 08 November 2005 21:06, Pete Wyckoff wrote:
> martin.schaffoener at e-technik.uni-magdeburg.de wrote on Tue, 08 Nov 2005 
21:50 +0200:
> > Don't know if it worked before; I only started using mpiexec now (0.80)
> > to replace all rsh-related stuff on our nodes.
>
> Here's a little patch to CVS that seems to work here, at least for
>     ./mpiexec -server &
>     ./mpiexec --comm=none -n 1 /bin/false
>
> Let me know if it seems to work for you and I'll check it in.  I
> think that the modified file hasn't been changed much since 0.80
> so it should patch cleanly to that distribution.

It does the trick. It applied to 0.80 with a constant offset of -1.

> Hrm, now that I think of it, is there any way that a pure server
> can exit cleanly?  Shouldn't it always return 1?  Let me know if
> you have any ideas.

Hm. If it is sent a signal to make it stop, I think it should exit cleanly if 
there are no connected clients. Otherwise, it should exit with an error. Or 
maybe it should just warn when sent SIGTERM if clients are still connected 
and continue running. In that case, maybe SIGKILL should be necessary to 
force it to stop.

What do you think?

Regards,
-- 
Martin Schafföner

Cognitive Systems Group, Institute of Electronics, Signal Processing and 
Communication Technologies, Department of Electrical Engineering, 
Otto-von-Guericke University Magdeburg
Phone: +49 391 6720063