[Bug 406397] Re: init: job stuck with expect fork/daemon when parent reaps child
tzeentch.gm at gmail.com
Thu Dec 8 08:30:55 UTC 2011
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
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
init: job stuck with expect fork/daemon when parent reaps child
Status in Upstart:
Status in “aiccu” package in Ubuntu:
Status in “upstart” package in Ubuntu:
Status in PLD Linux Distribution:
Wrong use of the expect fork stanza can create job with status
job stop/killled, process nnn
without any process nnn running on the system.
As an example the following avahi.conf should have used
"expect daemon", but will instead create a stuck job.
stop on stopping dbus-system
exec avahi-daemon -D
/Emil Renner Berthing
To manage notifications about this bug go to:
More information about the foundations-bugs