[mrtg] Re: Per run numbers

[Paul C. Williamson]

Not that I want to get into a p!$$!ng match, but no matter 
what you call them (values, counters, whatever), it is the 
last value read.  If you subtract the .old value from the .log 
value, you will end up with the exact amount transferred 
during the time period between .old and .log.

So, I can tell you that the line:

1005053113 243327423 2177424193

shows one of two things.  Either how much you have 
transferred since rollover of this value, or how much 
you have transferred since the startup of this device.

So yes, in reality, you should check it every 300 seconds
or 330 seconds from the last timestamp.  Using the second 
way should ensure that you do not miss a run of mrtg.

Paul

>>> Tuc <tuc at ttsg.com> 11/06/01 08:33AM >>>
> 
> 
> The first line has the actual time and value of the last 
> time the values were read.  
>
        No, the first line is the time, and the value of the
COUNTERS.  Not, that I know of, the amount of transfer last time.
We have machines that barely transfer more than 100K, yet the 
.log has :

1005053113 243327423 2177424193
1005053113 1090 31139 1090 31139
1005052814 1282 32327 1282 32327

        You can't tell me that 243327423 is how much we transfered. 
>
> The .old file has the same 
> information, but for the previous run.  So if the collections 
> were exactly 300 seconds apart, the timestamps should 
> be 300 seconds apart.  You should only need the first 
> line of the .log file.
>
        Sorry, disagree. By itself no. Linked with .old, no either. The
problem is that now I need to calculate when rollover occurs.  The other
issue is if I miss a run, how can I tell? 

                Tuc/TTSG Internet Services, Inc.
 
> Paul
> 
> >>> Tuc <tuc at ttsg.com> 11/05/01 08:20PM >>>
> 
> Hi,
> 
> 	We are trying to write a program that'll make decisions on each run
> of MRTG.  
> 
> 	The problem we are having is there is no place (We know of, doesn't
> mean there isn't) that we can get the results of the LAST poll. We can read
> the .log file, but it doesn't have the current, just average and maximum.
> 
> 	The logthresh isn't guaranteed to run, since we actually need it to
> do "Logthreshing", so fudging it to 0 isn't possible.
> 
> 	Looking for suggestions...
> 
> 		Thanks, Tuc/TTSG Internet Services, Inc.
> 
> 
> --
> 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 
> 
> 
> 
> --
> 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 
> 
> 



--
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