I had the same problem with Upstart 0.6.5. Job locked at the 'killed' state when the process Upstart waited for didn't even exist. This is quite a serious problem as:
1. Can happen when the job 'expect fork|daemon' stanza does not match what the process really does. And when it happens fixing the job description won't help, as a job with same name cannot be started any more. 2. Even worse: the system won't even shut down properly – it will stay waiting for the 'killed' job to finish which will never happen. Not good, when the shutdown is reboot during remote trouble-shooting. The solution seem 'obvious' to me: don't wait for a process that doesn't even exist (even in a 'zombie' state). Or do I miss something? -- init: job stuck with expect fork/daemon when parent reaps child https://bugs.launchpad.net/bugs/406397 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
