suvayu ali wrote: > On Sat, Mar 24, 2012 at 10:46, Frantisek Hanzlik <franta@xxxxxxxxxxx> > wrote: >> IMO it is problem in newer bash versions, but yet more I suspect >> when it may be any cripled systemd behavior at init 0/6 (sorry, i >> want say poweroff.target/reboot.target ;), whether systemd (in >> order to halt/reboot computer several microseconds faster) kill >> bash before it is able save their stuff. > > This is just a ridiculous claim. Do you have any evidence to support > this claim? I haven't, therefore I ask there when somebody have same problem, and how I should diagnose this issue. I not know, how reproduce it, it seems occur pure randomly and rarely - but I'm sure it occur at least in 8-10 cases at several different F15/F16 i686 machines. Why You think this claim is ridiculous? - it may be bash bug, why not? In F15/16 is new 4.2 line, maybe it introduce some different way with history treating, is insafe when several bash instance for same user ends simultaneously, etc. - why it could not be systemd bug? When is servicing 0/6 runlevels in similar way as SYSV init/upstart before, then send SIGTERM and then SIGKILL to processes - and when it kill bash before is able write history, then what? - one another reason tackled me. I very often use Midnight Commander (mc), which probably run another bash process as its child. Then perhaps problem may occur when at exiting mc it kill child bash before bash write its history. I have no idea for other reasons to this problem. What seems You ridiculous here? -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
