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

[Clint Byrum]

It seems to me that upstart could forget about a pid if it can verify
that it has in fact disappeared. I've seen quite a few people bit by
this bug in #upstart on Freenode and on various forum sites. Because I
think the impact is perhaps higher than we might have originally
anticipated, I'd suggest that upstart devs raise the priority to High.

-- 
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 “upstart” package in Ubuntu:
  Invalid
Status in “upstart” package in Debian:
  New
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/406397/+subscriptions