[mythtv-commits] Ticket #11238: Master backend can shutdown in spite of active local frontend
MythTV
noreply at mythtv.org
Wed Nov 14 23:23:35 UTC 2012
#11238: Master backend can shutdown in spite of active local frontend
------------------------+----------------------------------
Reporter: peper03@… | Type: Patch - Bug Fix
Status: new | Priority: minor
Milestone: unknown | Component: MythTV - General
Version: 0.26-fixes | Severity: medium
Keywords: | Ticket locked: 0
------------------------+----------------------------------
On a combined BE/FE system, the frontend does not always register with the
backend, which can lead to the backend shutting down due to the idle
timer.
The BackendConnectionManager usually ensures a connection to the backend
by querying the 'Master host prefix'. On a combined BE/FE this prefix can
be retrieved directly without having to communicate with the backend and
no connection is made.
If the user starts the frontend but performs operations (e.g. listening to
NetRadio) that do not need to query the backend, no connection will ever
be made and the backend will continue to count down the idle timer.
If the user stays in the main menu for at least 15 seconds after starting
the frontend, the ThemeUpdateChecker will cause a connection to the
backend to be made but if he or she is not in the main menu when the 15
second timer expires, the check is not made.
The attached patch ensures that querying the master host prefix will
always result in a connection to the backend.
Whether this is the cleanest solution is debatable as querying the master
host prefix does not need to imply that a connection will be made to the
master BE, but that is the behaviour already assumed by the
BackendConnectionManager.
This problem may be the cause of #10971
--
Ticket URL: <http://code.mythtv.org/trac/ticket/11238>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list