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

[Tim Nicholas]

I personally think being different from everyone else is a problem.

Also, this is the sort of bug that should be architecturally impossible
in an init system. init shouldn't have to track state perfectly to
function on the basic level of 'start jobs' 'stop jobs'.

I understand there are benefits for workstations with this (boot speed
etc), but for a server upstart is notably less good than old-school init
- even without the bugs, it's still very opaque - what with its lack of
logging etc.

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