Cheshire Cat Computing

Hello All , Does anyone know of a method to place the Vertical Rate bar on the Right side of a Graph .

I've tried a few searches here to see if anyone might have done so or asked about doing , to no avail . So I am asking outright if anyone has done so .

Tia , JimL

If you have the absolute latest beta of Routers2, it has support for dual Y-axis graphs. You could define a second Y-axis with scaleshift of 1:0 (multiply by 1 and add zero) and then you'll get an axis on both sides?

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Hello Steve , I take it that the 'Latest Beta' is the one shown on the Router.cgi page ?

Tia , JimL

ps: I'll work under that as a assumption the statement above will render a 'Yes' back .

Hello Steve , Thank you , Your suggestion worked like a charm .

Btw , CONGRADULATIONS !-)

Hope to hear from you soon('sh) .

JimL

Hello Steve (& All) , what have I done wrong here ? I inserted the twp lines , ...

routers.cgi*Ylegend2[_]:
routers.cgi*ScaleShift[_]: 1:0

In one cfg file & it ran fine , inserted into the rest & these messages are filling up my mail spool . Any insgiths very welcome .

using routers2.cgi-2.21b1-20091014

ERROR: Line 33 (routers.cgi*Ylegend2[_]:) in CFG file (/var/www/htdocs/router2cgi/cfg/mo-rtr03.cfg) does not make sense

Also just tried mrtg-2.16.3 , same message still .
I was under the impression that those two routers.cgi options had been in for some time . It's definatelty mrtg spewing the message .
Anybody have a idea where (or what) I am doing wrong ?

What is really bothering me is that those two options worked flawlessly before a (unscheduled) reboot occurred , Now they spew that message & the rrd's are not updating of course .

Tia , JimL

Ok , I found my Stupidity is still active .

routers.cgi*Ylegend2[_]: ""

Note the "" above , that cured the message . Now to update the rest of the cfg's .

Thank you for putting up with me . JimL

MRTG should ignore any directives with a '*' in them; however it doesnt like empty data (IE nothing after the ':' ), particularly in a global or default definition. This is the source of the whinge, as you realised.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11