Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] Treatment of SIGHUP by mpirun
From: Jon Hitchcock (Jon.Hitchcock_at_[hidden])
Date: 2010-04-22 14:17:39

"mpirun -version" says "mpirun (Open MPI) 1.3.3"

>>> Ralph Castain <rhc_at_[hidden]> 22/04/2010 19:14:18 >>>
Which OMPI version?

On Apr 22, 2010, at 12:04 PM, Jon Hitchcock wrote:

> If a user connects to a cluster using SSH, starts an MPI program which contains an infinite loop, and then breaks the SSH connection, the processes running the MPI program continue to run on the compute nodes and they have to be killed manually.
> To investigate this, I found that if the user types Control-C (or sends SIGINT to mpirun), mpirun says "killing job...", and on each compute node the orted process and the process running the MPI program are killed.
> However if SIGHUP is sent to mpirun, it says "Hangup" and exits, and on each compute node the orted process is killed but the process running the MPI program continues to run.
> This is with Rocks 5.3 and Open MPI. There is no batch scheduler. The MPI program is just:
> #include "mpi.h"
> main(int argc, char **argv) {
> MPI_Init(&argc, &argv);
> while (1) ;
> MPI_Finalize();
> }
> I have two questions. Is this the behaviour I should expect? Is there an easy way to kill the processes?
> Thanks, Jon Hitchcock
> _______________________________________________
> users mailing list
> users_at_[hidden]

users mailing list