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

Given that the PID would be killed pretty much as soon as it started and
that you're most likely to trigger this while writing an unstart job for
a daemon, I'd agree that the potential for serious problems is low.

However, I don't think this is a user error/mistake, some daemons are
just more awkward than others, may require scripts, etc., I don't think
it's reasonable to expect every daemon out there to be re-written to
play well.

-- 
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:
  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
_______________________________________________
pld-bugs mailing list
pld-bugs <at> lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-bugs