Cheshire Cat Computing

When using MRTG with RRDTool/routers2.cgi, it is not really intended to be run in this way. For efficiency, it generates the graphs only when someone wants to view them.

Presumably you are using a different program to access the graph files created in the temporary working directory, rather than using the routers2.cgi frontend? This is not the way it is intended to be done, and so it is naturally a bit awkward.

If you are doing this in order to archive the graphs, may I suggest you do it a different way -- instead, use the Archiving or rrd-archiving utilities? If you enable archiving in the routers2.conf, then you can click on the 'archive' button (or call the script with the appropriate options) in order to let routers.cgi archive the graph itself. Alternatively (and probably better) you can periodically run the rrd-archive script in the extras directory, which will archive all of the .rrd files (as defined) and will then allow the frontend to select a date to view the graph of.

Steve

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

As per the other open question thread, the aim was to create a quick cast iron graph backup routine, which thanks to your assistance is now fully operational - daily graphs generated at 0700 of the next morning and copied into a different network location by a script.

I will now do the R'n'D required to also create data/graph archiving as you have suggested.

Again, thanks for your prompt help.

Phil.

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