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

[john miller]

Could upstart track an arbitrary number of forks? instead of limiting to
1 (expect fork) or 2 (expect daemon) could expect N be supported?

Also here is a bash script to exhaust the pid space if your system does
not have ruby.

pass the pid upstart is waiting for as an argument like this
exhaustPIDspace.sh 11920

#!/bin/bash

usleep 1 &
firstPID=$!
#first lets exhaust the space
while [ $! -ge $firstPID ]
do
    usleep 1 &
done

while [ $! -le $1 ]
do
    usleep 1 &
done

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