upstart

wrong start condition in upstart-file-bridge.conf

Bug #1235387 reported by Steve Langasek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart
Fix Committed
Undecided
Unassigned
upstart (Ubuntu)
Fix Released
Undecided
Unassigned

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

Related branches

lp:~vorlon/upstart/lp.1235387
James Hunt: Approve
Diff: 25 lines (+7/-1)
2 files modified
ChangeLog (+6/-0)
extra/conf/upstart-file-bridge.conf (+1/-1)
lp:ubuntu/saucy/upstart
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Fri, 04 Oct 2013 11:35:18 -0700

Changed in upstart (Ubuntu):
status: New → Fix Released
Dimitri John Ledkov (xnox)
Changed in upstart:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.