Got it. I now see each proc reporting the signal. Thank you.
On 25 July 2017 at 11:45, r...@open-mpi.org wrote:
> Again, you are sending the signal to just the one process whose pid you
> specified. We don’t pick that signal up and propagate it. If you signal the
> pid of mpiexec itself, then yo
Again, you are sending the signal to just the one process whose pid you
specified. We don’t pick that signal up and propagate it. If you signal the pid
of mpiexec itself, then you’d see every proc report it.
> On Jul 25, 2017, at 11:40 AM, Marc Cooper wrote:
>
> Even this method of raising sig
Even this method of raising signal from user to mpiexec results in signal
handling by only one process. I've modified my earlier example where each
process publishes its pid, and I capture the pid and raise the signal using
'kill -SIGUSR1 ' from another terminal.
// test.c
void handle_signal(int
I’m afraid we don’t currently support that use-case. We forward signals sent by
the user to mpiexec (i.e., the user “hits” mpiexec with a signal), but we don’t
do anything to support an application proc attempting to raise a signal and
asking it to be propagated.
If you are using OMPI master, o
Hi all,
I'm working to understand signal handling in OpenMPI. I read that "Open MPI
will forward SIGUSR1 and SIGUSR2 from mpiexec to the other processes". My
question is that is this feature enabled by default installation.
The scenario is that one MPI process raises a SIGUSR1, which has to be
de
