This also happens when you use "expect fork" or "expect daemon" combined
with "script", Upstart ends up following the first spawned child whose
exit status is reaped by the shell. For example:
script
ARGS=$(cat /etc/default/myservice)
exec /sbin/myservice $ARGS
end script
Upstart ends up with the pid of "cat", and never receives SIGCHLD for
it. So stays in running indefinitely, and when you try and stop it,
hangs in "stop/killed"
** Summary changed:
- init: job stuck with expect fork/daemon when parent reaps child (avahi-daemon)
+ init: job stuck with expect fork/daemon when parent reaps child
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu)
Status: New => Triaged
** Changed in: upstart (Ubuntu)
Importance: Undecided => Low
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
