https://bugzilla.novell.com/show_bug.cgi?id=652633
https://bugzilla.novell.com/show_bug.cgi?id=652633#c4
Dr. Werner Fink changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |werner@novell.com
InfoProvider| |kasievers@novell.com
--- Comment #4 from Dr. Werner Fink 2011-02-16 08:47:12 UTC ---
Hmmm ... AFAICS from source of util-linux-2.19-rc1 from factory the
signal handler at http://git.kernel.org/ is identical with those of
util-linux-2.19-rc1
static void
sig_handler(int signal)
{
if(child_pid)
kill(-child_pid, signal);
else
got_sig = 1;
if(signal == SIGTERM)
kill(-child_pid, SIGHUP); /* because the shell often ignores
SIGTERM */
}
.. and AFAICR this does not happen with sysvinit. The question rises:
is it possible for the shell to save its history. Or do you have an
strace around to see if the signals will reach the shell in the correct
order (SIGTERM, SIGHUP) and the shell has the possiblity and enough time
to save its history to disk *before* the final SIGKILL and umounting the
file system.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.