touch-packages team mailing list archive

[James Hunt <1381075@xxxxxxxxxxxxxxxxxx>]

The most appropriate way to do this would probably be to use apport to
check for respawn limit messages in:

- the system log, and
- the users $HOME/.xsession-errors file.

Even at the default upstart log priority of 'message', when a job
reaches the respawn limit, upstart will log a message to one of the logs
above like this:

    init: foo respawning too fast, stopped

So apport, or some such utility could watch for these messages using
inotify and raise an informational error that would be visible on
errors.u.c.



** Also affects: apport (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1381075

Title:
  [ubuntu-touch] upstart should report applications that hit respawn
  limit to errors.ubuntu.com

Status in “apport” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  We have important system and session services that we rely on being
  running and functional.

  If such a component hits the upstart respawn limit for any reason, we
  should be able to get a report that something is seriously wrong.

  Inspiration for this bug as per the discussion in:
  https://bugs.launchpad.net/ubuntu/+source/indicator-
  network/+bug/1371320

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1381075/+subscriptions