[mrtg] Re: locking the graph's scale

[Nejaa Halcyon]

I currently use the basic MRTG with no RRD additions. Switching was 
something I've always thought about doing but never saw a reason to change 
because MRTG was working so well and it always did what I needed it to do. 
It looks like I've got my reason now.

Thanks for all you input folks,
Nejaa

On Mon, 19 Apr 2004 11:09:27 +1200, Steve Shipway 
<s.shipway at auckland.ac.nz> wrote:

> If you use the routers2.cgi frontend to MRTG, then you can use the 
> 'Rescal'
> button on the page to try two different rescalings (based on current 
> average
> values) to eliminate spikes in the graph.
>
> You can also specify a rigid upperlimit for the graph at 3Mbit, but this
> will mean that it always scales to this, and never closer (unless you
> rescale of course)
> routers.cgi*UpperLimit[ezwf]: 375000
> routers.cgi*Options[ezwf]: rigid
> UpperLimit defaults to MaxBytes, so you may only need the second of these
> lines.
>
> If you are not using the routers2.cgi frontend, though, I don't know of a
> way to achieve this.
>
> Steve
>
> ---
> Steve Shipway: ITSS, University of Auckland
> Email: s.shipway at auckland.ac.nz  Web: http://www.steveshipway.org/
> ** We can only discover new oceans when we have the **
> ** courage to lose sight of the shore.              **
>

-- 
"Hackers and academics have uncovered one Windows security hole after 
another, turning Microsoft into a frantic little Dutch boy at the dike 
without enough fingers."
-- David Pogue, The New York Times

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