|
From: | David Kaspar [Dee'Kej] |
Subject: | Re: Race condition in handling SIGHUP |
Date: | Thu, 28 Apr 2016 17:23:49 +0200 |
Because systems using a networked password database can hang at a priority
that doesn't interrupt the system call when a SIGHUP arrives.
That code is written the way it is to accommodate the much more common
case of users exiting a shell by hitting the `close' button on their
terminal window, which causes the terminal emulator to send one or more
SIGHUPs to the shell process, usually while readline is active. You want
shell to try and save the history in this case, since that's what users
expect.
[Prev in Thread] | Current Thread | [Next in Thread] |