> "parsing the MRTG log file AND writing a report based on the > contents" is what I really meant to say. > > Kind of like awstats for MRTG if anyone is familiar with this.
By far the easiest way to achieve this is to move to RRDTool. There are many reporting scripts for RRD-based databases, since this is much more flexible. It's also more efficient! You can switch your existing MRTG over to use RRD without too much trouble. There is a conversion utility to change .log files to .rrd, and you just have to add one line to the .cfg files to let MRTG know. You will also find a huge performance improvement on data gather. The downside is that you will need to install a CGI script - such as routers2, 14all or mrtg-rrd - to display the graphs (which are now created on demand) but this will give you more flexibility in any case. Then, there is a Perl library (and also a PHP library) to access and query the RRD database from any script you care to write. Rather than try to parse the old .log files, and have to deal with locking issues, I'd go this way. Steve -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
