[mythtv-users] Slave Backend requirements
Michael T. Dean
mtdean at thirdcontact.com
Wed Aug 21 13:07:21 UTC 2013
On 08/20/2013 10:34 PM, Michael Watson wrote:
> I run my Frontends as SBE (with a configured Dummy Tuner) to assist
> with commercial detection, whilst I know I can use mythjobqueue to
> achieve this, with Mythjobqueue the SBE/Frontend will not shut down
> whilst not in use, mythjobqueue is great for a 24x7 system.
I'm not sure what, specifically, you mean by this, but since Feb 2012
mythjobqueue only holds a blocking connection when it's actually
processing jobs, but changes to a non-blocking connection (which allows
master backend shutdown) when it's idle. (This has been in releases
since 0.25.)
http://www.gossamer-threads.com/lists/mythtv/commits/502795#502795
So a mythjobqueue server won't prevent the master backend from shutting
down, unless it's actually running a job (which requires master backend
presence/availability). And a mythjobqueue server will take
significantly less resources than a remote backend.
If you're saying that the master backend won't send out a message
telling the mythjobqueue system to go to sleep, that's true, but then
again, that's only useful on a machine with tuners that the master
backend may decide to use at some time that the remote backend can't
predict. On a machine that doesn't have tuners that may be needed at
some unknown point in the future, the machine can simply shut down when
it desires. So, you could use the frontend idle shutdown capability or
mythshutdown to shut down the computer when idle.
I don't know if mythfrontend's idle shutdown capability checks job queue
status, but I know mythshutdown does, so you may need to use mythshutdown.
Mike
More information about the mythtv-users
mailing list