Comment 12 for bug 252997

Revision history for this message
In , Laurent (laurent-redhat-bugs) wrote :

Description of problem:

upstart does not restart daemons when these ones terminate too rapidly. Daemons should be respawned after a while .
On previous distributions releases (Fedora/RH) the init process issued a new respawne cycle every 5 minutes. Upstart does not.

Version-Release number of selected component (if applicable):
0.3.X releases of upstart but newer releases seem to have the same lack.
cf
https://bugs.launchpad.net/upstart/+bug/252997

How reproducible:

On pervious inittab / old init process
the previous line added to inittab
test:2345:respawn:date >>/tmp/deblg.txt 2>&1

issued the following results :
Mon Jul 20 13:22:58 CEST 2009
... 8 more run
Mon Jul 20 13:22:58 CEST 2009
Mon Jul 20 13:27:59 CEST 2009
... 8 more run
Mon Jul 20 13:27:59 CEST 2009
Mon Jul 20 13:33:00 CEST 2009
... 8 more run
Mon Jul 20 13:33:00 CEST 2009
...etc

The same 'date >>/tmp/deblg.txt 2>&1' added into a file
in /etc/event.d/ results in the command executed 10 times.
No more respawn cycle appears every 5 minutes.

This missing respawn cycle make migration of some processes
from init to upstrat more difficult.