Of the list you provided, what bits aren't currently covered by:
- /usr/share/doc/ifenslave/README.Debian.gz
- /usr/share/doc/ifenslave/examples/*
- ifup/ifdown/interfaces manpage
Based on those, this seems to cover:
1) ifup manpage says that ifupdown processes the interfaces in the order they
are listed in /etc/network/interfaces. This obviously means that if there are
dependencies between interfaces, you should make sure the ordering is correct
2) allow-bondX is never mentioned in the Ubuntu documentation but auto always
is
3) It means there are no hardcoded list of slaves for that bond (slaves are
assigned through bond-master in their own interface definitions as per the
examples).
5) See 1), you are supposed to first have all the physical devices, each with
the right bond-master set, then the bond device itself with bond-slaves none.
In this case, bringing up any of the physical devices will bring up the bond.
If none of the physical devices exist by the time you bring up the bond, it'll
wait for 5 minutes for a slave to appear on the system.
6) See README.Debian.gz and the examples
** Changed in: ifenslave (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279651
Title:
[doc enhance] Add example or comment for /etc/network/interfaces to
man page
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifenslave/+bug/1279651/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
