[Bug 831606] Re: "respawn" does not start job again

[Clint Byrum]

Indeed, its not entirely clear, but in the (well maintained) man page
for job syntax, 'man 5 init', its stated that 'respawn' and 'respawn
limit' are two different stanzas.

Marking Invalid. I tried to convert this into a question but Launchpad
didn't want to.

** Changed in: upstart
       Status: New => Invalid

** Changed in: upstart (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/831606

Title:
  "respawn" does not start job again

Status in Upstart:
  Invalid
Status in “upstart” package in Ubuntu:
  Invalid

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/831606/+subscriptions