[mrtg] Preventing spikes from "wrapping" counters?

[Travis Veazey]

Using mrtg on a 64-bit Ubuntu system, logging with rrdtool; we use mrts to
view the resulting graphs. I'm using a Perl script, shorewall_stats.pl (
http://www.nightbrawler.com/code/shorewall-stats/), to query accounting
information from Shorewall and record it with mrtg.

My problem is that any time Shorewall is restarted (e.g. to load
configuration changes), the counters all get reset to 0 and mrtg appears to
assume that this means it has wrapped around, resulting in huge spikes on
our graphs. This makes them near impossible to read (to say nothing of the
false "maximum" and traffic totals now reported). Is there any way to get
mrtg to not make this assumption that a suddenly-low value means a wrapped
counter?

Strangely, this problem does not exist on an otherwise-identical 32-bit
system.

Any help would be greatly appreciated.

-Travis

-- 
"The reader is entertained by the journey of another, but the writer is the
changer of worlds."
- D'ni Proverb

0100111001000101010100100100010000100001
Stephen Leacock<http://www.brainyquote.com/quotes/authors/s/stephen_leacock.html>
- "I detest life-insurance agents: they always argue that I shall some
day
die, which is not so."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/mrtg/attachments/20100215/2e2e8476/attachment.htm