[Bug 406397] Re: init: job stuck with expect fork/daemon when parent reaps child

[Clint Byrum]

Tim, I'm sorry that you're experiencing the issue. I believe that squid
may have always had this issue and we only stirred it up by updating
squid.

There is a really scary workaround available which is to create a
program that exhausts the pid-space until tracked pid exists again, and
then upstart will be able to re-attach and kill it...

http://heh.fi/tmp/workaround-upstart-snafu

I do think that we may need something a little less perfect than a full
rewrite of the ptrace tracker that we could possibly backport to lucid.
There seems to be a missing command that would allow an administrator to
tell upstart to just forget about an instance.

-- 
You received this bug notification because you are subscribed to PLD
Linux.
https://bugs.launchpad.net/bugs/406397

Title:
  init: job stuck with expect fork/daemon when parent reaps child

Status in Upstart:
  Triaged
Status in “aiccu” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  Invalid
Status in PLD Linux Distribution:
  New

Bug description:
  Hi

  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
  respawn
  expect fork
  exec avahi-daemon -D

  /Emil Renner Berthing