[mrtg] Advice: monitoring GPS based clock

[Steve Shipway]

> routers.cgi*UpperLimit[$target_name]: -120
> routers.cgi*LowerLimit[$target_name]: -200
...
> routers.cgi*Options[$target_name]: noo nototal nopercent fixunit
> routers.cgi*Graph[$target_name]: $graphtarget_name noo $color
...
> Do I need to set routers.cgi*UpperLimit[$graphtarget_name]: -120 to make
> this work right?  I'm running 2.21beta of routers2.cgi.  I think my reading
> of the routers2 docs suggests routers.cgi*UpperLimit was only applicable to
> targets and not to pseudo graph targets.
> 
> I tried to use routers.cgi*Options[] rigid, but that ignores the
> LowerLimit[] directive....

I am assuming that you are referring to the userdefined graph over the multiple components, not the individual target graph.

The UpperLimit and LowerLimit options are not inherited by a userdefined graph; so, you should have

routers.cgi*UpperLimit[$graphtarget_name]: -120
routers.cgi*LowerLimit[$graphtarget_name]: -200

to define the options for the userdefined graph as well.  If you also use

routers.cgi*Options[$graphtarget_name]: rigid

then this will force the userdefined graph to be between these Y values, regardless of the data values.

Since the limits, and the data, are all negative this can cause some odd behaviour in some situations.  You might like to upgrade to v2.22 of routers2.cgi from the website as this fixed a minor bug in this regard?

Steve

Steve Shipway
ITS Unix Services Design Lead
University of Auckland, New Zealand
Floor 1, 58 Symonds Street, Auckland
Phone: +64 (0)9 3737599 ext 86487
DDI: +64 (0)9 924 6487
Mobile: +64 (0)21 753 189
Email: s.shipway at auckland.ac.nz
 Please consider the environment before printing this e-mail 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4928 bytes
Desc: not available
Url : http://lists.oetiker.ch/pipermail/mrtg/attachments/20110907/1ece34dd/attachment.bin