It seems to me that upstart could forget about a pid if it can verify that it has in fact disappeared. I've seen quite a few people bit by this bug in #upstart on Freenode and on various forum sites. Because I think the impact is perhaps higher than we might have originally anticipated, I'd suggest that upstart devs raise the priority to High.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/406397 Title: init: job stuck with expect fork/daemon when parent reaps child To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/406397/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
