[Bug 1072759] Re: sendsigs should only ignore upstart job with specify 'stop on' explicitly

[Steve Langasek]

> /etc/init.d/sendsigs currently ignores all upstart jobs, assuming Upstart
> will stop all associated job processes.

Not exactly; it assumes upstart will stop all associated job processes
/which need to be stopped before unmounting the filesystem at shutdown/.
There are some jobs, such as plymouth, which are expected to continue
running until shutdown, and are expected to work correctly on a read-
only root filesystem.  Now, the plymouth job happens to have a 'stop'
condition, but that's actually irrelevant to the nature of what sendsigs
is doing.

If there are upstart jobs on the system that are failing to shutdown and
therefore causing havoc, we should fix that... but not by making changes
to the sysvinit sendsigs script, IMHO.  And I'm not aware of any real
jobs that currently fall into this category.

** Changed in: sysvinit (Ubuntu)
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1072759

Title:
  sendsigs should only ignore upstart job with specify 'stop on'
  explicitly

Status in “sysvinit” package in Ubuntu:
  Won't Fix

Bug description:
  /etc/init.d/sendsigs currently ignores all upstart jobs, assuming
  Upstart will stop all associated job processes.

  However, this is only true if those jobs explicitly specify a 'stop
  on' condition, otherwise they will persist.

  /etc/init.d/sendsigs should be modified to only ignore upstart jobs
  that are running and which have an explicity 'stop on' condition. See:
  http://upstart.ubuntu.com/cookbook/#list-all-jobs-with-no-stop-on-
  condition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1072759/+subscriptions