[Bug 1235387] Re: wrong start condition in upstart-file-bridge.conf

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.10-0ubuntu5

---------------
upstart (1.10-0ubuntu5) saucy; urgency=low

  * extra/conf/upstart-file-bridge.conf: fix the start condition to
    comply with the intent, that we start the file bridge only once
    the filesystem is up. (LP: #1235387)
 -- Steve Langasek <steve.langasek at ubuntu.com>   Fri, 04 Oct 2013 11:35:18 -0700

** Changed in: upstart (Ubuntu)
       Status: New => Fix Released

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

Title:
  wrong start condition in upstart-file-bridge.conf

Status in Upstart:
  New
Status in “upstart” package in Ubuntu:
  Fix Released

Bug description:
  The bzr log for extra/conf/upstart-file-bridge.conf claims that the
  job is meant to start once the filesystem is fully mounted.  But the
  current start condition doesn't guarantee that at all; instead, it
  starts the file bridge as soon as the *first* mount point is mounted
  by mountall.  This needs to be 'start on filesystem'.

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