<br><br>
<div><span class="gmail_quote">On 5/4/05, <b class="gmail_sendername">David George</b> <<a href="mailto:david@thegeorges.us">david@thegeorges.us</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On 5/4/2005 1:47 PM, Christopher David Petersen wrote:<br><br>[snip]</blockquote>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">> developer. Basically, the software runs as root on all your backends.<br><br>Sounds nice, but why does it need to run on each backend?
</blockquote>
<div> </div>
<div>Actually, it doesn't. Just on systems where you want to monitor something. It's a more generic solution that can be used for more than just MythTV. The code will eventually allow people to write simple plug-ins to monitor whatever their hearts desire.
</div>
<div> </div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">> The program gets its settings from 4 new tables (which will soon be<br>> controlled via MythWeb), and stores the results of it's analysis
<br>> in another new table (the led_status table).<br><br>Why would you need new database tables. I haven't looked into the job<br>status, but all the other things are easily retrieved through the<br>backend protocol. The guide data status has been in there since Isaac
<br>accepted my patch adding it to the backend server.</blockquote>
<div> </div>
<div>All the new tables except one, hold configuration data for the various things you want to monitor. The other table holds the results of all the analysis.</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">> The program can also be run on a front-end, where it reads the status<br>> information from the status table and controls the 8 LEDs connected to
<br>> the parallel port. The hardware costs about $10 at RadioShack, and the<br>> software is free.<br>><br>> I currently have MythLEDd running on my combined backend/frontend<br>> controlling 3 LEDs. Red means tuner one is recording, green means the
<br>> machine is either transcoding or commercial flagging, blinking yellow<br>> means low disk space, and solid yellow means low EPG data.<br><br>Hmm, same here. Actually I use bicolor LEDs for each of the 8 tuners
<br>(green=tuner available but not recording, red=tuner recording, off=no<br>tuner or tuner error), and have a system status light that comes on if<br>guide data < 7 days or will flash on low disk space or guide data < 3
<br>days. I almost forgot, there is also a buzzer inside that will start<br>beeping if communications with the backend are lost. The tuner LEDs do<br>support tuners on slave backends.</blockquote>
<div> </div>
<div> </div>
<div>Your solution looks beautiful. But seems beyond my target budget (<$10) and diffently beyond my soldering skills. The parallel port, resistor, LED solution is supper easy and cheap.</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Check out the link in my sig for pictures of the LEDs and the source<br>code for the monitor program which runs on the frontend (and doesn't
<br>require any database or backend changes).</blockquote>
<div> </div>
<div> </div>
<div>This is a really nice looking box! I wish I weren't cheap :)</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Of course, the OP was asking for something simple... oops :-)<br><br>--<br>David<br><br>HDTV frontend I'm working on (pictures, mythmon source)
<br><a href="http://mythhd.info">http://mythhd.info</a><br><br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div><br>