Given that the PID would be killed pretty much as soon as it started and that you're most likely to trigger this while writing an unstart job for a daemon, I'd agree that the potential for serious problems is low.
However, I don't think this is a user error/mistake, some daemons are just more awkward than others, may require scripts, etc., I don't think it's reasonable to expect every daemon out there to be re-written to play well. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
