[mythtv-users] Best Way to Run Commercial Detection Jobs Not On Master Backend
Drew Tomlinson
drew at mykitchentable.net
Thu Dec 26 23:35:45 UTC 2013
On 12/25/2013 5:15 PM, Jon Heizer wrote:
>
>
> On Dec 25, 2013 1:45 PM, "Drew Tomlinson" <drew at mykitchentable.net
> <mailto:drew at mykitchentable.net>> wrote:
> >
> > I've been running a combo front/backend on an Athlon dual core box
> for many years. It works but it's a bit low powered for commercial
> detection jobs, especially for HD streams.
> >
> > I've recently replaced an old P3 600 mhz unix server with a Xeon
> based processor and have built a VMWare ESXi host. I plan on
> rebuilding my old server as a VM on this box. However I will have a
> lot of available CPU power here and wondered about building another VM
> who's sole purpose is to take some of the commercial detection load
> off of my master backend.
> >
> > I'm not sure how to do this. At first I assumed I would need to
> build a slave backend. However I have seen other threads that talk
> about there being no reason to build a slave backend unless there are
> tuners attached as mythjobqueue can provide the function with much
> less overhead.
> >
> > Can anyone point me in the right direction to get this started? I
> have built a VM with Mythbuntu, choosing the slave backend option, but
> don't really know how to get it to help with commercial detection jobs
> on the master.
> >
> > Thanks,
> >
> > Drew
>
> Run mythtv-setup like you are configuring a slave back end and then
> just have mythjobqueue run instead of mythbackend.
>
Hi Jon,
Thank you for your reply. My master backend has 1 storage group
(default) containing 4 local disks/directories:
/tv0/record
/tv1/record
/tv2/record
/tv3/record
I assume I need to mount these same directories on my slave and then
create a storage group that contains them?
Just making sure that the slave needs access to the drives directly and
it's not done via some MythTV protocol.
Thanks,
Drew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20131226/98ead1a2/attachment.html>
More information about the mythtv-users
mailing list