If we move usage.db file instead of deleting, then it can be used later for publishing via cgi-bin.Ġ 0 * * * mv /tmp/usage.db /mnt/usbdrive/wrtbwmon/usage-$(date '+%Y.%m.%d').Flowmon helps you to Identify bottlenecks and resolve latency issues caused by networks, servers and applications. If you are interested in the traffic of the current day, then usage.db file has to be deleted every day at midnight. * * * * * & wget some_url/usage.db -O /tmp/usage.db * * * * * & cp /mnt/usbdrive/wrtbwmon/usage.db /tmp/ġ5 * * * * cd /tmp & ftpput -u username -p password usage.db. If you put it in RAM, schedule a periodic backup task and restore it if missing, for example :ġ5 * * * * cp /tmp/usage.db /mnt/usbdrive/wrtbwmon/ It will be written to very often, so it is not recommended to put it on flash memory, but should be put in RAM (like in /tmp/ directory). The /tmp/usage.db file is a database file that contains the accounting records. */30 9-23 * * * /opt/wrtbwmon/wrtbwmon update /tmp/wrtbwmon.db peak */30,59 4-8 * * * /opt/wrtbwmon/wrtbwmon update /tmp/wrtbwmon.db offpeak */30 0-3 * * * /opt/wrtbwmon/wrtbwmon update /tmp/wrtbwmon.db peak In this example the off-peak counters get updated from 4:00 to 8:59, the peak counters the rest of the day. Note: this only works with kallisti's version.īandwidth usage can be separated to peak and offpeak times. You can change loglevel of cron in order to write only error messages into syslog by:
0 kommentar(er)
