Karl Newman wrote: > <snip> > > If > > a. you have an automated way to collect power supply stats over the long > term and build plots (using tools like Perl and gnuplot) > > > Just a note about that point: newer versions of lm_sensors (maybe > version 3+?) come with sensord, a daemon which is designed for > configurable logging of sensor data and also to notify about alarms, and > there are tools to generate a web page and graph of the variables. > I suspect I'm going to need to set up some data collection. I'm running Gentoo, and it appears that though I'm running lm_sensors-2.10.7 at the moment, I have lm_sensors-3.1.1 available, so I need to look into logging.
In addition, though I don't know if I need it any longer, I'm still using the supplemental "tune.sh" script at mythbackend startup that does a dummy capture or two on each card, and throws it away. This is/was because the audio didn't work right on the first capture. I need to beef up this script to collect some statistics, and in particular add Andy's suggested "v4l2-ctl -d /dev/video0 --log-status" as a normal part. There look to be 4 parts... 1 - Build up a more detailed picture of "normal" 2 - Keep current boot statistics so if it turns out that I have the dread red screen, I can compare that with a normal boot. 3 - Autodetect problems so I can recover promptly, and not lose recordings. 4 - Figure out what the real problem is. It looks like it starts with adding data collection to "tune.sh" and adding logging to lm_sensors. Dale _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
