The scripts I have are not really in a releasable state at this time as there are parts of it that are specific to my overall environment. After I finish my upgrade to r5.5 I'll work on putting then into shape. Having said that, I can describe the basic method for tracking when the front end goes idle. I run a process that is launched at boot time. It wakes up every 2 minutes and measures the amount of CPU time used by the front end process. If the amount of CPU time does not change for 15 checks in a row, it declares that the front end is idle. I ran some tests, and as few as 3-4 clicks on my remote to navigate up or down on a menu will chalk up 1 second of CPU time on a Pentium D930 3.0 ghz processor, so it doesn't take much to make the front end look busy.
I did a quick cut down of the script, so this version is untested -- use at your own risk
.
Code:
#! /bin/sh
log=/var/log/mfemon.log
stime=120
idle=15
echo "mfemon started `date`" > $log
while true
do
sleep $stime
xxx=`ps uU mythtv | egrep "mythfrontend" | awk ' { print $1,$2,$10,$11 }'`
if [ "$xxx" != "" ]; then
echo "$xxx `date`" >> $log
tail -$idle $log > $log.2
mv -f $log.2 $log
cnt=`cut -d" " -f1,2,3,4 $log | sort -u | wc -l`
if [ $cnt = 1 ]; then
pkill mythfrontend
echo "Mythfrontend stopped `date`" >> $log
fi
fi
done
log=/var/log/mfemon.log
stime=120
idle=15
echo "mfemon started `date`" > $log
while true
do
sleep $stime
xxx=`ps uU mythtv | egrep "mythfrontend" | awk ' { print $1,$2,$10,$11 }'`
if [ "$xxx" != "" ]; then
echo "$xxx `date`" >> $log
tail -$idle $log > $log.2
mv -f $log.2 $log
cnt=`cut -d" " -f1,2,3,4 $log | sort -u | wc -l`
if [ $cnt = 1 ]; then
pkill mythfrontend
echo "Mythfrontend stopped `date`" >> $log
fi
fi
done
Marc