Trunk now has better handling of failures in the child process whilst
still inside Upstart's own code, specifically it can catch an exec()
failure and obtain the error number.

In practice, there's little we can realisitically do; but we do at least
log the problem ("No such file or directory") and fail both the job and
event that spawned it.

This means that a distribution can deal with /bin/sh missingness with
any of:

  start on stopped sulogin failed
  exec /sbin/omgtheskyisfalling

or:

  start on stalled/failed
  exec /sbin/omgtheskyisfalling

etc.

** Changed in: upstart
       Status: Triaged => Fix Committed

-- 
upstart utterly fails when /bin/sh symlink disappears
https://bugs.launchpad.net/bugs/65024
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to