[mrtg] Re: rateup writing *.log file incorrectly - post 2

[Alex van den Bogaerdt]

paul beard wrote:
> 
> sure did. it seems that making all the zeroes non-zero value made 
> it unstick itself. Now the logfile is updating.
> 
> Alex van den Bogaerdt wrote:
> 
> > 
> > Memory.  This is not increasing over time so you should use
> > the gauge option.  Did you?

So, what you're basically saying is that there's a bug in MRTG
(or: rateup) where a gauge value isn't making it into the log.
When you manually enter values on the second line, the problem
disappears.  Is this right?

Can you check the following two cases please?

1) setup a new target from scratch, without the gauge option, let
   this run a few times then enter the gauge option
2) setup a new target from scratch, with the gauge option present
   from the beginning

Do you get similar results? Need they be solved and if so, does it
work predictably?

cheers,
-- 
   __________________________________________________________________
 / alex at slot.hollandcasino.nl                  alex at ergens.op.het.net \
| work                                                         private |
| My employer is capable of speaking therefore I speak only for myself |
+----------------------------------------------------------------------+
| Technical questions sent directly to me will be nuked. Use the list. | 
+----------------------------------------------------------------------+
| http://faq.mrtg.org/                                                 |
| http://rrdtool.eu.org  --> tutorial                                  |
+----------------------------------------------------------------------+

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
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