Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] Open MPI's 'mpiexec' trash output of program being aborted?
From: Ralph Castain (rhc_at_[hidden])
Date: 2014-02-27 12:43:04


Not intentional, but I suspect it's a race condition you are seeing. I'll have to look to see where it is getting lost

On Feb 27, 2014, at 9:32 AM, Paul Kapinos <kapinos_at_[hidden]> wrote:

> Dear Open MPI developer,
>
>
> Please take a look at the attached 'program'.
>
> In this program, we try to catch signals send from outside, and "handle" them. In case of different signals different output has to be produced.
>
> When you start this file directly, or using 'mpiexec' from Intel MPI, and then abort it by Ctrl-C, the output "SIGINT received" is written to file and to StdOut.
>
> When you start this file using Open MPI's 'mpiexec', the output is written to file, but *not* to StdOutput - 'mpiexec' seem to nick it.
>
> Is that behaviour intentionally? (it is quite uncomfortable, huh)
>
> Best
>
> Paul Kapinos
>
> P.S. Tested versions: 1.6.5, 1.7.4
>
>
>
>
>
> --
> Dipl.-Inform. Paul Kapinos - High Performance Computing,
> RWTH Aachen University, IT Center
> Seffenter Weg 23, D 52074 Aachen (Germany)
> Tel: +49 241/80-24915
> <testoutput.py>_______________________________________________
> devel mailing list
> devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel