[Bug 1091783] Re: init: failsafe main process killed by TERM signal

[Sworddragon]

I think the most annoying thing is that this causes an entry in dmesg.
Wouldn't it be possible that failsafe can exit itself with 0 if it
detects that the system has booted successfully instead of waiting for a
TERM signal? For example instead of sending the TERM signal Upstart
could emit an own event for this which failsafe also listens on the
"stop on" stanza. Or doesn't this work?

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

Title:
  init: failsafe main process killed by TERM signal

Status in “upstart” package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 13.04 dev with upstart 1.6.1-1ubuntu1. On booting my
  system I'm seeing in /var/log/kern.log the line "Dec 18 18:17:46
  ubuntu kernel: <12>[   19.939989] init: failsafe main process (1033)
  killed by TERM signal".

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