#3 Unexpected behaviour when plotting gauges

[RDJ]

Hi,

I'm using RTG 0.7.4. Apologies up front if this turns
out to be my
own fault. I'm trying to use RTG to monitor
attributes other than
just traffic, and to this end I've modified the manner
in which RTG
is storing data quite a bit.

As an example, I've been trying to plot a graph of CPU
frequency
vs time. The data is being inserted into the RTG
database by an
external script as a gauge value - ie each reading is
independent
of the previous one. If the first reading is X, then X
is stored,
if the second Y, then Y is stored.

When trying to plot this data I was getting very
strange graphs.
Further investigation showed that the graph.ymax value
appeared to be getting set to arbitrary, generally
large values.
This doesn't appear to affect rate-based graphs, but was
buggering up gauge plots.

Initialising "rate->max = 0;" around line 373 (in
calculate_total)
fixed the problem, and doesn't seem to have had any side
affects.

-Ronan