So I installed MRTG yesterday, compiled from source (2.10.15). However, when I run 'env LANG=C /usr/local/mrtg-2/bin/mrtg /etc/mrtg.cfg' It returns in a few seconds, no errors but when I refresh the page the line that says 'The statistics were last updated X' stays the same. If I do an ls -la on the output directory all the last modified times are the same as what is displayed on the webpage except for a few which correspond to the time when I first ran MRTG.
The date corresponds to the 2nd time that I ran the program. Linux, RH 9, 2.4 thanks, -copen /etc/profile and enter this 'export env LANG=C' at the end of file logout and then login again open /etc/crontab 0-59/5 * * * * root /usr/local/mrtg-2/bin/mrtg /etc/mrtg/this can execute mrtg every 5 min Originally posted by kkj open /etc/profile and enter this 'export env LANG=C' at the end of file logout and then login again open /etc/crontab 0-59/5 * * * * root /usr/local/mrtg-2/bin/mrtg /etc/mrtg/this can execute mrtg every 5 min Ok found out that I didn't have snmpwalk installed, so I downloaded and compiled that.
You also need to set up a cron job to regenerate the configuration periodically (see below).
Note that our header template starts MRTG as a daemon (see below also).
# /etc/crontab: system-wide crontab # Unlike any other crontab you don't have to run the `crontab' # command to install the new version when you edit this file # and files in /etc/cron.d.
The stars say to run this command on all days and times.
On Free BSD, MRTG comes with an initd script by default and you can kick it off on boot with something like the following in file which kicks it off every five minutes (it will daemonise the first time and further cron jobs will have no effect).
If you use this method, you will need to have your periodic update script restart / stop the daemon when the configuration changes.
I haven't tried to recompile all MRTG but is going to be my next step. :) Mario Forer Mario Network System Administrator [email protected] Time alone can prove the worth of friendship.As the time passes, we lose the false one and keep the best.I have found the asnwer, "Each graph is build from the data in its own *and *files.So if you copy these to your production server you conserve all historic data from the test box.Before doing that, though, try running on a separate line at the bottom of /etc/crontab.