Re: [OMPI users] Treatment of SIGHUP by mpirun

2010-04-22 Thread Ralph Castain
Sounds like a bug - the processes should have died via SIGTERM, followed by SIGKILL. I know we had some problems in that regard, but I'm not sure if the fixes came into the 1.3.3 release or not. You might try updating to the 1.4.2rc1 tarball and see if that helps. I recently fixed a similar iss

Re: [OMPI users] Treatment of SIGHUP by mpirun

2010-04-22 Thread Jon Hitchcock
"mpirun -version" says "mpirun (Open MPI) 1.3.3" >>> Ralph Castain 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 connec

Re: [OMPI users] Treatment of SIGHUP by mpirun

2010-04-22 Thread Ralph Castain
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

[OMPI users] Treatment of SIGHUP by mpirun

2010-04-22 Thread Jon Hitchcock
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 typ