etc.
Not saying it cannot be done - just indicating that there were
reasons why it wasn't initially done other than "we just didn't
get around to it". :-)
(If I had to guess, I think the user is asking because some other
MPI implementations implement this kind of beh
"our implementation prohibits this." :-)
My fault - should have been clearer.
From:
devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On
Behalf Of Ralph Castain
Sent: Friday, June 02, 2006 9:12 AM
To: Open MPI Developers
Subject:
t; -Original Message-
> From: devel-boun...@open-mpi.org
> [mailto:devel-boun...@open-mpi.org] On Behalf Of Pak Lui
> Sent: Friday, June 02, 2006 11:37 AM
> To: r...@lanl.gov; Open MPI Developers
> Subject: Re: [OMPI devel] SIGSTOP and SIGCONT on orted
>
> I agree that
riday, June 02, 2006 9:12 AM
To: Open MPI Developers
Subject: Re: [OMPI devel] SIGSTOP and SIGCONT on orted
Jeff Squyres (jsquyres) wrote:
Just curious -- what's difficult about this? SIGTSTP
and SIGCONT can be caught; is the
tting the stop to freeze the application
processes.
Thanks!
--------
*From:* devel-boun...@open-mpi.org
[mailto:devel-boun...@open-mpi.org] *On Behalf Of *Ralph Castain
*Sent:* Thursday, June 01, 2006 10:50 PM
*To:
(If I had to guess, I think the user is asking
because some other MPI implementations implement this kind of behavior)
Thanks!
From:
devel-boun...@open-mpi.org [mailto:devel-boun...@open-mpi.org] On
Behalf Of Ralph Castain
Sent: Thursday, June 01, 2006 10:50 PM
To:
MPI
implementations implement this kind of behavior)
Thanks!
From: devel-boun...@open-mpi.org
[mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain
Sent: Thursday, June 01, 2006 10:50 PM
To: Open MPI Developers
Subject: R
Actually, there were some implementation issues that might prevent this
from working and were the reason we didn't implement it right away. We
don't actually transmit the SIGTERM - we capture it in mpirun and then
propagate our own "die" command to the remote processes and daemons.
Fortunately,
The main reason that it doesn't work is because we didn't do any thing
to make it work. :-)
Specifically, mpirun is not intercepting SIGSTOP and passing it on to
the remote nodes. There is nothing in the design or architecture that
would prevent this, but we just don't do it [yet].
> -Orig
