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

[Steve Langasek]

Public bug reported:

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'.

** Affects: upstart
     Importance: Undecided
         Status: New

** Affects: upstart (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: upstart
   Importance: Undecided
       Status: New

-- 
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:
  New

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