FS#46890 - [systemd] systemctl poweroff etc. kill session not graciously
Attached to Project:
Arch Linux
Opened by Manuel Schneider (manuelschneid3r) - Tuesday, 27 October 2015, 19:51 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 18 June 2016, 13:05 GMT
Opened by Manuel Schneider (manuelschneid3r) - Tuesday, 27 October 2015, 19:51 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 18 June 2016, 13:05 GMT
|
Details
Description:
This is rather vague, because I dont know how to find more sophisticated information. From what I see systemctl poweroff kills the session hard. At least my application has no time to save its settings. Additional info: Everything is up to date. Steps to reproduce: e.g. rm .bash_history, run bash, enter some commands, finally do "systemctl poweroff -i", restart machine an recognize that bash hat no time to save its history to .bash_history. |
This task depends upon
Closed by Dave Reisner (falconindy)
Saturday, 18 June 2016, 13:05 GMT
Reason for closing: Fixed
Additional comments about closing: Seems fixed, maybe by https://github.com/systemd/systemd/commi t/fbffe09d692c1bd92e3d552031d096e77c3886 51
Saturday, 18 June 2016, 13:05 GMT
Reason for closing: Fixed
Additional comments about closing: Seems fixed, maybe by https://github.com/systemd/systemd/commi t/fbffe09d692c1bd92e3d552031d096e77c3886 51
Comment by
Evangelos Foutras (foutrelis) -
Wednesday, 28 October 2015, 04:50 GMT
Comment by
Dave Reisner (falconindy) - Sunday,
12 June 2016, 19:00 GMT
Sounds like this bug:
https://github.com/systemd/systemd/issues/317
I can't reproduce this with systemd v230. Shell history even shows
the last command as being 'systemctl reboot'.