Something like the attached can be put into /usr/share/upstart/sessions/ and it will detect when system-level and session-level jobs hit their respawn limit.
We could then use whitelists to identify the desired behaviour (restart job, reboot, etc) for particular services. ** Attachment added: "respawn-watchdog.conf" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1381075/+attachment/4243843/+files/respawn-watchdog.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport 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: Confirmed Status in “upstart” package in Ubuntu: Confirmed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
