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

[Guido Scalise]

Anand, there's a rather harsh workaround using a ruby script you can download here:
http://heh.fi/tmp/workaround-upstart-snafu

It worked for me, but, as I said, the approach is quite "aggressive".

Basically it forks new dummy, short-lived, processes until the PID
sequence restarts. Then, when one of these subprocesses gets the
"blocked" PID, it waits until upstart kills it, thus unlocking the job's
state.

I didn't see any side effects, but YMMV.

-- 
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