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

[Michael Gliwinski]

Yeah, as Scott already mentioned, pidfiles introduce their own set of
problems, but also they aren't a solution for all use cases.  E.g. the
daemon I was dealing with does not have any way to write out a pidfile,
forks multiple times, requires a script to do some setup before it's
launched, and is a third party and closed source, so I can't do anything
about this mess ;)

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