forcemerge 469950 458985 thanks Nicolas François, le Fri 28 Mar 2008 23:30:25 +0100, a écrit : > On Sat, Mar 08, 2008 at 09:33:54PM +1300, Jasen Betts wrote: > > > > starting some tasks (eg: top - see Debian Bug #416976) in an xterm after > > using su can lead to undesirable behavior if the xterm is closed. > > That's arguably the case even without su ;) > > > After a little testing, it seems that the child process never gets > > the SIGHUP which it normally gets when su is not used (or it is used > > and logged out of) and then the xterm is closed > > su does not block any SIGHUP. > > I did not follow #416976. Samuel and Thomas, do you think there were > anything wrong in the su behavior?
This is a duplicate of 416976. Su is behaving correctly. The kernel is behaving correctly: it doesn't allow xterm to send signals to su sessions for good reasons ;) The problem is in bash that doesn't properly handle the case when it's not permitted to SIGHUP all of its patriarchy. Samuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
