/etc/init.d/networking restart and "sudo restart networking" aren't
supported ways of restarting the network, actually, we don't support any
way of bouncing the whole network config as it's configured through
event based bringup.
Rather than copy/paste half the code of ifenslave, could you instead
post your current /etc/network/interfaces as well as the output of
"ifdown -a -v" and "ifup -a -v"?
As a reminder, ifupdown is entirely sequential it's therefore required for the
ordering to be roughly:
- loopback
- primary physical interface (bond member)
- any other physical interface (bond member)
- bond interface
- any virtual interface (vlan, bridge, ...) based on top of the bond
If the interfaces aren't listed in precisely that order, "ifup -a" will
hang (though the boot itself won't as it's using events to bring up
individual interfaces rather than using ifup -a).
** Changed in: ifenslave (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269921
Title:
networking services restart hangs due to missing
/etc/network/run/ifenslave.* files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifenslave/+bug/1269921/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
