Re: A target arithmetic issue

> So I take it MRTG uses 32bit values internally when it gets 
> 32bit data back from a target? I guess that sorta makes sense 
> and would certainly explain what I am seeing. 

I think what happens is that MRTG notices it is retrieving 32bit counters,
and so assumes they will wrap on the 32bit boundary instead of the 64bit
boundary.  When the numbers get too big, it triggers the wrap-detection code
by mistake.  If you use 64-bit counters then the wrap-detection code doesnt
get tickeld.

But this is all guesswork based on the behaviour of MRTG.

Steve

--
Unsubscribe mailto:mrtg-request <at> list.ee.ethz.ch?subject=unsubscribe
Archive     http://lists.ee.ethz.ch/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://lists.ee.ethz.ch/lsg2.cgi