On Fri, 6 Aug 2004 15:38:27 -0400, "Britt Tabor" wrote in <[EMAIL PROTECTED]>: > I have posted a couple of Qs for tis issue but still researching > and have not found an answer.
1) most cases are solved by showing folks a part of config file. > but what happens is the file is just overwritten. 2) .log file will be *just* overwritten in normal case too. > as you can see the .old file has a value for the 1091819968 time > stamp but in the .log file this timestamp has been reset to 0 0 0 0 3) isn't this a famous MaxBytes/AbsMax problem? > 2004-08-06 15:19:29 -- --log: Called /usr/bin/rateup /var/www/mrtg/ > routers/rey1-a100_21 1091819968 -z g 2023150802 1196177688 128000 > c #00cc00 #0000ff #006600 #ff00ff -t -b -d Z GMT+4 k 1000 i > /var/www/mrtg/routers/rey1-a100_21-day.png 128000 128000 400 100 > 1 1 0 300 0 4 1 Your AbsMax may be 128000 since rateup called with '-z g 2023150802 1196177688 128000 ', also it implies unknaszero and gauge. When in-value(2023150802) is greater than max-value(128000), with unknaszero is set, it will be treated as 0. Same rule apply to out-value calculation. I'm not sure if I'm right :) -- Takumi Yamane <[EMAIL PROTECTED]> -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
