This does seem to be a systemd problem that is affecting a lot of different applications -- basically any application that would like a SIGTERM on reboot/shutdown so that it can save or clean up resources gracefully.
See https://bugzilla.redhat.com/show_bug.cgi?id=1141137 (upstream systemd issue) https://bugzilla.redhat.com/show_bug.cgi?id=1170765 (systemd issue affecting bash's attempt to save history) https://github.com/cockpit-project/cockpit/issues/1155 (systemd issue affecting cockpit) http://lists.freedesktop.org/archives/systemd- devel/2014-October/024452.html (discussion) My suggestion would be that you open a new bug report against systemd in Ubuntu 15.04 and mention that it is affecting bash and mosh (and probably every other application that would like to clean up gracefully on shutdown or reboot). ** 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
