[Bug 1338788] Re: startpar-bridge: does not notice, if upstart jobs are skipped

[Steve Langasek]

If the upstart job has bailed out in pre-start, it has not started. The
correct thing to do here is to notice the 'stopped' condition and have
startpar treat that as a failed start - so that startpar does not wait
for the job indefinitely, and also so that startpar does not start the
dependent services.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1338788

Title:
  startpar-bridge: does not notice, if upstart jobs are skipped

Status in “sysvinit” package in Ubuntu:
  New

Bug description:
  startpar-bridge: does not notice, if upstart jobs are skipped

  For example, if init.d script is enabled, yet equivalent upstart job
  bails-out in pre-start.

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