Removing the assignment of proc->script solves this problem for me. If in future we need to know how the process was started, we should store that information elsewhere, because implicit and explicit use of the shell are not exactly equivalent. Patch attached.
This and the patch in bug #1169614 give me a clean shutdown on current saucy. ** Patch added: "Don't set proc->script on implicit shell use" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1181789/+attachment/3713952/+files/srd.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181789 Title: second call of 'initctl start' leads to fork instead of exec ('mount: / is busy' during shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1181789/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
