> > I'm trying to get a better idea about how my stuff performs, and are > > now looking for ideas on where any changes on art(4) interfaces are > > recorded. Can we please have some general "play loud" option that would > > send everything to syslog using eg. kern.info? Seeing malloc() failures > > is probably a good thing, but a better thing is seeing a line flap if > > it does, possibly with a differentiation between local and remote end. > > Offhand, I don't see anything to this effect in the code (CVS), but > > that may well be me. > > > > Link state changes are generally not logged by the kernel. > Only lmc(4) and sppp(4) tend to fill the syslog with "useless" status > messages. The other interfaces I use seem to "behave". > If link state changes need to be logged than it should be done in an > interface independent way so that all interface will profit from it.
I agree with Claudio that network interfaces should be as silent as possible. They are network interfaces, not chatter boxes. > It should be no issue to track the interface state in userland by > listening on the routing socket. man route, and read up on 'show'
