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

[Mark Hurenkamp]

While implementing a new upstart script, i also ran into this problem,
and am now stuck with a job waiting for a non-existing pid.

I think the worst-case scenario has not been mentioned yet, which is
that when the actual pid does appear, it will be killed by this job
thinking it is the process it has been waiting to kill. This could be a
harmless process (or even created for that purpose by a script mentioned
above), but it could also be a critical process. Thus the bug is less
harmless than it appears to be.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
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:
  Confirmed
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

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