[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Mon, 7 Sep 2009, Paul Hirst wrote:
On Fri, 2009-09-04 at 22:59 +0100, Gordon Henderson wrote:If you're reading the counters yourself, be aware that they're 32-bit and will wrap at some point, so you need to be able to cater for that.You just set me wondering, now I have a 64 bit workstation.... br0 Link encap:Ethernet HWaddr 00:30:05:c3:a1:b7 inet addr:10.181.0.131 Bcast:10.181.7.255 Mask:255.255.248.0 inet6 addr: fe80::230:5ff:fec3:a1b7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:46359241 errors:0 dropped:0 overruns:0 frame:0 TX packets:23601903 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:55191207739 (55.1 GB) TX bytes:2031853646 (2.0 GB) Hurrah! No wrapping at 4GB anymore!
This is one area where 32-bit is going to suffer - the default 5 minute sample interval for mrtg is too short for a GB network interface running flat-out ..
On the downside my Pidgin instance was using ~12G of virtual memory the other day. (1.1G resident) Apologies for generally babbling and not adding anything useful :-)
Don't we all ;-) Gordon -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html