[Bug 522197] Re: init: shouldn't log a warning/error when a job fails with a status in "normal exit"

[Clint Byrum]

Marking Triaged since this has been fixed upstream, and should land in
Oneiric as soon as the delta between Ubuntu and Upstream is resolved.

For those who cannot boot, I'm afraid this isn't the actual reason your
system cannot boot, so please don't expect *this* issue to be fixed in
previous stable releases. As annoying as it is, its not eating data or
anything like that, so IMO it is not suitable for a stable release
update.

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

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

Title:
  init: shouldn't log a warning/error when a job fails with a status in
  "normal exit"

Status in Upstart:
  Fix Released
Status in “upstart” package in Ubuntu:
  Triaged

Bug description:
  When a job exits with a non-zero exit status or with a signal, this is
  logged with a high priority (warning/error).  If the syslog daemon
  isn't running yet, this ends up on the system console.

  If the exit status or signal is a "normal exit" reason for the
  process, they shouldn't be anywhere near as high priority and
  certainly shouldn't spam the console.

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