[Bug 831606] [NEW] "respawn" does not start job again
Launchpad Bug Tracker
831606 at bugs.launchpad.net
Tue Aug 23 06:01:23 UTC 2011
You have been subscribed to a public bug:
The conf file for nsd has these stanzas:
start on runlevel [234]
stop on runlevel [!234]
respawn limit 5 100
exec ...
The job can be started manually using /sbin/start, but once the process
exits, the job just goes back into state "stop/waiting". It doesn't
look like init makes any attempt at re-starting it. I cannot find any
relevant entry in log files either, apart from auth.log recording that I
did "sudo /sbin/start ...".
Requests:
* respawn should respawn the job
* upstart/init should log its actions, or reasons for inaction
==========================
$ cat /etc/issue.net
Ubuntu 10.04.2 LTS
$ init --version
init (upstart 0.6.5)
Copyright (C) 2010 Canonical Ltd.
This is free software; see the source for copying conditions. There is
NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
** Affects: upstart
Importance: Undecided
Status: New
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Tags: respawn
--
"respawn" does not start job again
https://bugs.launchpad.net/bugs/831606
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to upstart in Ubuntu.
More information about the foundations-bugs
mailing list