touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

It's still more or less the same, except that every unit and scope is
being shut down individually. "man systemd.kill" has the details.

-- 
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 does not send SIGTERM first on shutdown

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Vivid:
  In Progress
Status in systemd package in Fedora:
  Unknown

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