Paul Durrant wrote:
On 24/05/07, Garrett D'Amore <[EMAIL PROTECTED]> wrote:
That's the way it is implemented in my workspace right now.... its just
that the logging functionality doesn't provide anything other than the
the up/down notification. Details have to be retrieved from dladm or
kstats.
Indeed, and I think up/down is too much information. That should also
be retrieved from stats.
Again, I think there is historical value here. (Of two kinds. First
there is the historical practice of having the data in the logs.
Second, there is value in being able to look back in time and see when
link came up, or was dropped.) Plus it allows an administrator to see
link status changes in real-time by doing: tail -f /var/adm/messages
(without having to write a special tool to monitor dladm.)
If we want to further suppress link status notices in the log, at least
with this change there will be only one place to do so (in the mac
layer) rather than in all the drivers.
For the moment I think having *some* record of *changes* is useful.
(You won't see a link that is down continuing to report multiple entries
in the log, unless there is something seriously wrong with the PHY where
it keeps establishing and dropping link. But that's a sign of a serious
problem that deserves logging anyway.)
-- Garrett
_______________________________________________
networking-discuss mailing list
[email protected]
