usptart-socket-bridge is not started on transition from runlevel 1 to 2

Bug #820682 reported by Clint Byrum
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

The upstart-socket-bridge upstart job uses

stop on runlevel [!2345]

but it starts on 'net-device-up IFACE=lo', which will not happen if the administrator manually puts the system in runlevel 1 for maintenance and the brings it back into runlevel 2.

Tags: runlevel1
Revision history for this message
Steve Langasek (vorlon) wrote :

'start on net-device-up IFACE=lo or runlevel [2345]' may be sufficient to fix this.

Changed in upstart (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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