networking is not actually brought down/up when moving to/from runlevel 1
Bug #752481 reported by
Clint Byrum
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
Fix Released
|
Medium
|
Stéphane Graber |
Bug Description
Binary package hint: ifupdown
Since the transition where networking has been handled largely by upstart, runlevel 1 does not bring down the network. Nor is it brought back up in any way by the transition back to runlevel 2.
Related branches
tags: | added: upstart |
tags: | added: runlevel1 |
Changed in ifupdown (Ubuntu): | |
assignee: | nobody → Stéphane Graber (stgraber) |
tags: | added: patch |
To post a comment you must log in.
So, starting with 12.10 both /etc/init/ networking. conf and /etc/init. d/networking will be the same upstart job and will include a post-stop target calling ifdown -a.
So in theory, I could change it to stop on switching to runlevel1 and start on switches to [2345], I'm just not convinced it's a good idea as we don't really support "ifdown -a && ifup -a" because of devices being hot-pluggable and sometimes requiring specific bring-up order that wouldn't be respected by calling "ifup -a".