This does seem to be a systemd bug that is affecting several applications -- basically any application that would like a SIGTERM on reboot/shutdown so that it can save or clean up resources gracefully.
Please see https://bugzilla.redhat.com/show_bug.cgi?id=1141137 (upstream systemd bug) https://bugzilla.redhat.com/show_bug.cgi?id=1170765 (bug affects bash's attempt to save history) https://github.com/cockpit-project/cockpit/issues/1155 (bug affects cockpit) http://lists.freedesktop.org/archives/systemd- devel/2014-October/024452.html (discussion) ** Bug watch added: Red Hat Bugzilla #1141137 https://bugzilla.redhat.com/show_bug.cgi?id=1141137 ** Bug watch added: Red Hat Bugzilla #1170765 https://bugzilla.redhat.com/show_bug.cgi?id=1170765 ** Also affects: systemd via https://bugzilla.redhat.com/show_bug.cgi?id=1141137 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd has wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
