On Mon, Mar 24, 2008 at 08:39:30PM +0000, Samuel Thibault wrote: > Oops, sorry, in my previous mail I was wrong: xterm doesn't send > SIGHUP to the foreground group, but just to the process group in has > started, i.e. bash, just like the kernel would indeed (since that's the > controlling process), so that's indeed a bit redundant, but keeping > it shouldn't do any harm. And it is indeed possibly needed for some > odd systems, on which rxvt not doing it would conversely have other > troubles (SUS's exit() page talks about 4.2 BSD).
ok (though 4.2 is quite old, some odd systems such as QNX may be relying on xterm to do this). > That said, sometimes there is no problem: when the pty gets closed > early, bash gets > ioctl(255, TIOCSPGRP, [5779]) = -1 ENOTTY (Inappropriate ioctl for device) > when it tries to disown the groups it has launched, and in that case the > kernel will SIGHUP the sudo'ed group, since not only bash failed to kill > it, but it also failed to disown it. > > So xterm is really not at fault here, it's bash that needs a fix. thanks for the info -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
pgpvrSTOgjBzB.pgp
Description: PGP signature
