Re: explanation of TCPLoss counters

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



In article <2b5e566d0809171242j56e1400ax2e00db8a133306c4@xxxxxxxxxxxxxx> you wrote:
> Right. Well, I appreciate your help.  I'm headed to the Linux Plumbers
> Conference tomorrow, so perhaps I will have something to talk about :)

Yes, what would be a nice topic: for example a Knowledge Base on all kinds of
kernel counters. Detailing not only the reason for a counter increase, but
also acceptable ranges (like 1% of received segments may be late) and
typical error sources (like broken hardware, wiring or some specific WAN
configuration). 

Especially for those network MIB counters I always thought it might
be good to monitor them more closely proactive, but thats a quite
environment specific task.

Commercial Unix or even BSD falvors tend to have at least more complete man
pages for those (which is not always really helpfull but a good start for
Joe average sysadmin).

Gruss
Bernd
--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux