This bug has not been fixed in Lucid and is still present in Natty (mitigated there by a fixed killall5 (which has no hard limit on the omitpid buffer). Ubuntu Lucid should either patch /etc/init.d/sendscripts as per in my original report (and attached patch), or backport killall5. This is a serious issue that affects proper shutdown.
In any case, the OMITPID code is... puzzling. Some PID numbers are granted immunity because at some point they were Upstart jobs. PIDs that stay alive accumulate multiple times in the OMITPIDS list during 10 iterations. PIDs can wrap around and the immunity could "save" an unrelated, non-upstart process. Could Steve Langasek (per debian/changelog) or someone else explain the OMITPID code? I understand that the list of upstart jobs is dynamical and re-query is needed, but why hang on to old PIDs from previous iterations? ** Patch added: "re-initialize OMITPIDS in every iteration" https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/665185/+attachment/1926827/+files/sendsigs-patch.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665185 Title: /etc/init.d/sendsigs fails to kill some processes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
