[mythtv] hello and question

Joseph Fry joe at thefrys.com
Wed Dec 19 20:00:13 UTC 2012


Or use something other than mythtv as your frontend.  UPNP is a simple
choice with a variety of low cost set top boxes (or even TV's with it
embeded).  XBMC is a good option to if it must run on a PC.


On Wed, Dec 19, 2012 at 2:30 PM, Raymond Wagner <raymond at wagnerrp.com>wrote:

> On 12/19/2012 12:10, Peter Hoopes wrote:
>
>> Hello MythTv dev's,
>>
>>         First, I wanted to thank you all for the work you do. I love
>> where MythTV
>> is going. We use it here at an independent school for capturing and
>> distributing video to several classrooms, laptops, and for video storage.
>> It works really well.
>>
>>         I suspect this isn't the right forum, but I'm hoping one of you
>> can point
>> me in the right direction. I'd like to implement a number of MythTV
>> Frontends across campus, but I would /really like/ to disable the RECORD
>> option. Unlike a person's house where they would normally want that
>> functionality at every station, I just want a host of playback (either
>> live or recorded) stations, as I'm afraid we're going to overload our
>> backend with recording by students (boarding school) and/or delete things.
>>
>>         It is possible to have a Frontend with that option disabled?
>> Again, I
>> figure I'm not in the right place - any pointers to another mail list or
>> developer would be great.
>>
>
> MythTV was never really designed with security against its users in mind.
> In order to record something, the frontend manually inserts a new recording
> rule into the database, and then sends a command to the backend using the
> internal protocol to perform a scheduling run. You could make a custom
> version of the frontend that rips out all the scheduling capability, but
> that wouldn't prevent anyone from building their own copy of MythTV and
> accessing it that way, or simply using the credentials in config.xml to
> poke the database directly.
>
> The easiest solution may simply be to run two systems, one accessible and
> one isolated. Have the isolated system perform all the recordings, and
> throw together some scripts tied into the event system that clone the
> recordings over to the public system. The public system wouldn't actually
> do any recording, but would only use dummy tuners to make mythbackend
> happy, so should anyone screw with it, it would be trivial to recover.
>
> ______________________________**_________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://www.mythtv.org/mailman/**listinfo/mythtv-dev<http://www.mythtv.org/mailman/listinfo/mythtv-dev>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-dev/attachments/20121219/d9e8de09/attachment.html>


More information about the mythtv-dev mailing list