touch-packages team mailing list archive

[Olli Niemi <1448259@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "Tester for missing SIGTERM"
   https://bugs.launchpad.net/bugs/1448259/+attachment/4383242/+files/test.c

** Package changed: mosh (Ubuntu) => systemd (Ubuntu)

-- 
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 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/ubuntu/+source/systemd/+bug/1448259/+subscriptions