Public bug reported: Binary package hint: sysvinit
If an Upstart job has no stop on condition, Upstart won't stop any instances of it. However, if a job has no stop on, but *does* specify respawn we have a potential problem at shutdown since: - /etc/init.d/sendsigs will attempt to kill the Upstart job PID(s) - Upstart will attempt to respawn the job until the respawn limit is reached. This bug is to change sendsigs such that it manually stops all Upstart jobs with no "stop on" *before* it generates the OMITPIDS list. See http://upstart.ubuntu.com/cookbook/#list-all-jobs-with-no-stop-on- condition for an example of how to list jobs with no "stop on" condition. This could be reworked to call "stop --no-wait $job" *before* we generate OMITPIDS from the output of "initctl list". ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750141 Title: /etc/init.d/sendsigs should stop Upstart jobs with no stop on condition -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
