On Tue, May 29, 2007 at 01:37:21PM -0700, Garrett D'Amore wrote: > Al Hopper wrote: > >>Casper.Dik at Sun.COM wrote: > > > >You seem to be missing the point - syslogging the interface name with > >speed and duplicity is useful in a couple of very practical ways: > > > >[SNIPPED: three cases not needing speed and duplicity info] > > > >All these examples are when you're working on the physical hardware. > >It's much faster to do this than search the product specific docs - > >and you don't have product specific docs if you've built the box and > >neglected to label the ethernet ports from a Solaris perspective. > > In all of these cases, you _do not_ need to know the link speed/duplex, > the "up" and "down" messages that I've proposed will address this need.
Yes, but others have given cases where speed and duplicity information is useful. > To re-state: > > * the link state change will be logged (going from down to up, or > vice versa), but the details of speed, duplex, channel, and other link > tunables will _not_ be part of the message that I've proposed. > > Hope that answers this concern. It doesn't. Nico --
