* Camiel Dobbelaar <c...@sentia.nl> [2011-02-04 15:30]: > On 4-2-2011 15:06, Stuart Henderson wrote: > > On 2011/02/04 14:37, Camiel Dobbelaar wrote: > >> On 4-2-2011 13:32, Henning Brauer wrote: > >>> * Camiel Dobbelaar <c...@sentia.nl> [2011-02-04 13:21]: > >>>> With hundreds of (vlan) interfaces, a shutdown takes quite a while. > >>>> Fix below. > >>> > >>> hmm. this relies on all carp interfaces being in the carp interface > >>> group. while that is the default, it is not necessarily so. > >> > >> I didn't know that a groupname takes precendence, neither did the > >> manpage. :-) > > > >> +If an interface group with that name exists, all interfaces in the group > >> +will be shown. > > > > seems it's more complicated than that - if you remove all interfaces > > from group carp, 'ifconfig carp' lists nothing: > > > > $ ifconfig |grep ^carp > > carp1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 > > carp2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 > > $ ifconfig carp > > $ > > > > but with another type, this doesn't apply: > > > > $ sudo ifconfig bge0 group em > > $ ifconfig em | egrep '(0: |groups:)' > > bge0: flags=28843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6> mtu 1500 > > groups: em > > $ sudo ifconfig bge0 -group em > > $ ifconfig em | egrep '(0: |groups:)' > > em0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> > > mtu 1500 > > groups: egress > > It looks like group "carp" is never removed from the system, even if it > becomes empty. That makes sense since some daemons use it as a default.
i don't think there is is special treatment for the carp group. but memory is fuzzy. we might very well "forget" to clean up when a group becomes empty. > But the manpage diff is still correct, isn't it? it's clear the manoage isn't right as-is, that's for sure ;) -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting
