On Thu, Jul 31, 2014 at 10:53 AM, Lennart Sorensen < lsore...@csclub.uwaterloo.ca> wrote:
> If you have a router with a 533MHz powerpc core and someone configures > 250 vlans that you have to bring up at boot, the difference between > /proc and netlink starts to make an enormous difference. Something like > the difference between booting in 2 minutes versus 45 minutes. > Preach it brother. ;) > Also if you do snmp and have a lot of interfaces to get data for, > netlink really helps a lot too. > Preach it brother. ;) For those of us who have worked in large storage environments, we run into similar issues with how Multipathing is handled. There are so many cases of these type of environments. I really like certified people to come in with good practices. Saves me the time to "de-program" them and start them on the road to recovery. ;) Also the ip command has much nicer syntax and supports stuff ifconfig > does not (or at least didn't for a long time, like multiple IPs on > an interface). > It's far easier to parse, when one is not writing direct calls to netlink itself This is in addition to nmcli (NetworkManager CLI), which is a higher layer that is being adopted. And then there are all of the new pushes for management, like OpenLMI. But that's getting way farther out. -- bjs
_______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
