-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It shouldn't be, since orterun should be sending a message (not
signals) to the orted's and have them shutdown. That mechanism has been
there before my addition. Ralph noticed some odd behavior with the
orted's living well after the orterun has exited. It's possible that
this is a result of the same bug. I was going to check that out
yesterday, but became sidetracked and didn't get to it. I'll take a
look this morning and see if I can't track this down.
Josh
On Sep 2, 2005, at 8:24 AM, Jeff Squyres wrote:
Josh --
Is this related to the orted signal traps you put in recently,
perchance?
On Sep 2, 2005, at 9:21 AM, Tim S. Woodall wrote:
Ctrl^C handling in orte seems to be broken. I know get a core
file for every orted that is spawned on remote nodes when
I attempt to kill a job via Crtl^C or orterun. This behaviour
has actually been around for about a week know. Anyone else
seeing this?
--
{+} Jeff Squyres
{+} The Open MPI Project
{+} http://www.open-mpi.org/
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
- ----
Josh Hursey
jjhur...@open-mpi.org
http://www.open-mpi.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFDGFqrAxXT7ehIlVwRAvqPAKCyJ3sf9nZ4wN4H1bMP0aLWZX5mBACeJUCV
2+5K2jnMxEhN94uDaxB32tg=
=w3ce
-----END PGP SIGNATURE-----
