On Tue, Nov 27, 2012 at 3:41 PM, Stéphane Graber <stgra...@stgraber.org> wrote: > It's not a bug. "ifup bond0" will configure the bond and wait until the > first slave joins to return, so it'll indeed "hang" but that's the > wanted behaviour.
Errr.... this is not what the documentation says (/usr/share/doc/ifenslave-2.6/README.Debian.gz): """ Using ifup on a master interface will call ifup for all slaves that are flagged with allow-bondX. (bondX being replaced by the master interface name). """ Instead, as you say the master interface just "hangs" and the slaves are never ifup'ed. So, either the documentation is incorrect, or ifup does not work as documented. > If you need to reconfigure your bond, you need to call "ifdown" on all > bond members, then on the bond interface, change your config and then do > "ifup" on all the bond members and then on the bond interface. Again, this is not what the documentation says (/usr/share/doc/ifenslave-2.6/README.Debian.gz): """ Using ifdown on a master interface will cause all slaves to be freed and disabled. The master is also cleaned-up to ensure reliable results if the master is brought up later. """ I'm not asking for `ifup` to be changed, but the docs should be consistent :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015199 Title: ifup does not work as documented with bonding interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/1015199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
