I added to crontab:
root@mythtv:/etc/cron.hourly# crontab -l
*/5 * * * * /usr/local/bin/run_rrd

The only problem I'm seeing is that the networking stats don't get updated.
I can run /usr/local/bin/rrd_traffic and get:

root@mythtv:/etc/cron.hourly# /usr/local/bin/rrd_traffic.pl
eth0 traffic in, out: 163058, 540323

After I run it manually, it shows the one snap shot on the Monitor page with mythweb.
Even if I put that script in to crontab or cron.hourly, it never seems to update.

Any ideas?

Thanks!

TiM

Same here. Working on it at the moment - will let you know what I find.

_________________
LinHES 7.1, Gigabyte GA-K8NXP-SLI m/b, Athlon 64 X2 4200+, 3Gb RAM, 80GB PATA (/ & /myth), 2TB SATA (/myth/tv), Gigabyte 8600GT component-out, 2x Dvico HDTV DVB-T Lite, 1x Hauppage HVR-2200 PCIe Dual, Harmony remote with Dvico IR receiver.

Edit /usr/local/bin/rrd_traffic.pl and add the path to the callson lines 38 &39 to ifconfig, grep and cut.

gbutters you officially rock my world. I've been swearing at that script for 2 days and I never would have picked up that fix.

Nice work!

_________________
LinHES 7.1, Gigabyte GA-K8NXP-SLI m/b, Athlon 64 X2 4200+, 3Gb RAM, 80GB PATA (/ & /myth), 2TB SATA (/myth/tv), Gigabyte 8600GT component-out, 2x Dvico HDTV DVB-T Lite, 1x Hauppage HVR-2200 PCIe Dual, Harmony remote with Dvico IR receiver.

Good eye! BTW - I changed these to:

to reduce the number of commands in the pipeline.

Updated.

Gbutters sorry I am not getting your post I don't have anything pointing to a path on line 38 and 39

Will put you where you want to be...

Sorry I had no problem editing the file and found the lines just not sure what to do with them
my $in = `ifconfig $_[0] |grep bytes|cut -d":" -f2|cut -d" " -f1`;
my $out = `ifconfig $_[0] |grep bytes|cut -d":" -f3|cut -d" " -f1`;

See my example which uses full pathnames for all the executables used.

Since these are being run by cron any assumptions about what is in your environment (especially your PATH) will tend to get you in trouble. Folks have had similar problems in the past with program guide grabbers that make unwarranted assumptions about the HOME variable being set...

Thanks tjc