I opened https://svn.open-mpi.org/trac/ompi/ticket/1144 to track this
issue.
On Aug 20, 2007, at 9:04 AM, Daniel Spångberg wrote:
Dear Sven,
I thought about doing that and experimented a bit as well, but
there are
some problems then: I need to relink the users code, registering an
atexit
Dear Sven,
I thought about doing that and experimented a bit as well, but there are
some problems then: I need to relink the users code, registering an atexit
function is tricky from the fortran code, and I still need to know whether
MPI_Finalize (and as it turns out MPI_Init as well, other
instead of doing dirty with the library you could try to register a cleanup
function with atexit.
Thanks,
Sven
On Friday 17 August 2007 19:59, Daniel Spångberg wrote:
> Dear George,
>
> I think that the best way is to call MPI_Abort. However, this forces the
> user to modify the code, whic
Dear George,
I think that the best way is to call MPI_Abort. However, this forces the
user to modify the code, which I already have suggested. But their
application is not calling exit directly, I merely wrote the simplest code
that demonstrates the problem. Their application is a Fortran p
The MPI standard state that the correct way to abort/kill an MPI
application is using the MPI_Abort function. Except, if you're doing
some kind of fault tolerance stuff, there is no reason to end one of
your MPI processes via exit.
Thanks,
george.
On Aug 16, 2007, at 12:04 PM, Daniel
Dear Open-MPI user list members,
I am currently having a user with an application where one of the
MPI-processes die, but the openmpi-system does not kill the rest of the
application.
Since the mpirun man page states the following I would expect it to take
care of killing the application
