https://bugzilla.novell.com/show_bug.cgi?id=801863 https://bugzilla.novell.com/show_bug.cgi?id=801863#c1 --- Comment #1 from Jiri Slaby 2013-02-02 19:31:12 UTC ---

users' history

I mean bash_history contents of course... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=801863 https://bugzilla.novell.com/show_bug.cgi?id=801863#c3 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jslaby@suse.com | --- Comment #3 from Jiri Slaby 2013-02-04 08:48:09 UTC --- The thing is that it did not use to happen, it started happening even recently (as I wrote it started around switch to 12.3 -- I'm using factory all the time). Now, I don't understand from your description, why does bash open bash_history? If it is "killed" by instant poweroff or crash it should not open .bash_history at all, right? Sad is that I have no idea how to debug that, but the issue proper painfull. BTW. doesn't it open the file with O_APPEND? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=801863 https://bugzilla.novell.com/show_bug.cgi?id=801863#c5 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com --- Comment #5 from Dr. Werner Fink 2013-02-04 09:30:59 UTC --- It does not open with O_APPEND every bash writes out a full ~/.bash_history as it may (re)sort the history, clearly locking is used for this. And this requires enough time if there are a lot of interactive bash programs are running. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=801863 https://bugzilla.novell.com/show_bug.cgi?id=801863#c7 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com --- Comment #7 from Dr. Werner Fink 2013-02-04 10:07:13 UTC --- (In reply to comment #6) ... all interactive shells do ignore SIGTERM but react on SIGHUP. Even upstream of systemd should know this fact;) The normal way is that if xterm is signaled by SIGTERM, it will signal the clients on the pseudo terminal line with SIGHUP that the terminal wll be closed. Maybe xterm has a bug (does not send SIGHUP for all clients on the terminal if a SIGTERM is catched) or systemd is ignoring this way. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=801863 https://bugzilla.novell.com/show_bug.cgi?id=801863#c9 --- Comment #9 from Dr. Werner Fink 2013-02-04 10:41:29 UTC --- The SIGTERM send to XTerm should cause XTerm to send SIGHUP to the shell running on the XTerm's terminal line. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=801863 https://bugzilla.novell.com/show_bug.cgi?id=801863#c11 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #11 from Dr. Werner Fink 2013-02-05 14:02:44 UTC --- (In reply to comment #6) (In reply to comment #10) Indeed the lines log_info("Sending SIGTERM to remaining processes..."); broadcast_signal(SIGTERM, true); log_info("Sending SIGKILL to remaining processes..."); broadcast_signal(SIGKILL, true); in http://cgit.freedesktop.org/systemd/systemd/tree/src/core/shutdown.c seems to very hard, that is there is no sleep between SIGTERM and SIGKILL. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=801863 https://bugzilla.novell.com/show_bug.cgi?id=801863#c13 --- Comment #13 from Dr. Werner Fink 2013-02-05 15:21:55 UTC --- (In reply to comment #12) there *is* a sleep: # Wait between last SIGTERM and the next SIGKILL # any argument specify a *path* of a process which # process identity should *not* be checked. rc_wait() { local -i etime=$SECONDS if test -f /fastboot ; then let etime+=2 else let etime+=6 fi [...] while test $SECONDS -lt $etime; do [...] done } from /etc/rc.status -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=801863 https://bugzilla.novell.com/show_bug.cgi?id=801863#c14 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|werner@suse.com |meissner@suse.com --- Comment #14 from Dr. Werner Fink 2013-04-08 11:47:10 UTC --- I can do nothing here, this happens is the bash is killed without SIGHUP and this shoulds not happen. @ Marcus: Please fix XTerm in such a way that bash is signaled with SIGHUP on closing the X connection. And please be aware that the bash might require some time to write out the history. Beside this I alos see this behaviour on 12.3 with tcsh as shell. Here also the close of the X connection causes XTerm to terminate/kill the shell(s) without using SIGHUP. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=801863 https://bugzilla.novell.com/show_bug.cgi?id=801863#c16 --- Comment #16 from Dr. Werner Fink 2013-04-08 12:56:11 UTC --- Wow, ten seconds are much more than the five seconds with SysVinit. -- 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.