touch-packages team mailing list archive

[Keith Winstein <1448259@xxxxxxxxxxxxxxxxxx>]

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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1448259

Title:
  Systemd has wrong kill mode on shutdown

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  It has been normal that applications first get the SIGTERM signal
  before SIGKILL on shutdown/reboot in order to successfully finish any
  pending tasks. Now it seem this logic has been changed to something
  else, causing problems to mosh and many others:

  https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982

  SIGTERM  suggestion can be seen here:

  http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8

  I created this error report to find out the correct way for
  applications to fix this problem or to create one fix to systemd,
  bringing back the old "BSD shutdown" functionality.

  This report is for Ubuntu 15.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1448259/+subscriptions