[mythtv-commits] Ticket #13136: Frontend Startup Improvement
MythTV
noreply at mythtv.org
Sat Sep 30 15:20:12 UTC 2017
#13136: Frontend Startup Improvement
------------------------------+-----------------------------
Reporter: pbennett | Owner: pbennett
Type: Patch - Feature | Status: new
Priority: minor | Milestone: 30.0
Component: MythTV - General | Version: Master Head
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
------------------------------+-----------------------------
Comment (by pbennett):
Thank you for looking at this.
If I understand correctly you feel it would be better if the frontend
starts up completely when the backend is already running, and goes into
the startup screen if the backend is down. I think that could be done very
easily, by suppressing wakeup until the user specifically selects "Retry"
on the startup screen. It would go though an initial round of trying and
failing to connect to the backend and then wait for the user to select one
of the options such as Retry or Exit. Upon Retry the wakeup would be
enabled.
In the case where the backend was already running, you would need to make
sure the frontend idle timeout is set so that if you are using the
frontend machine for something else mythfrontend can go into idle and the
backend can shut down. When the frontend is idle and the backend shuts
down, the frontend will theoretically wake the backend on any key stroke,
however it can take many minutes to respond to the key stroke. That
situation does not work well, due to the long timeouts involved. I tried
and failed to find an easy solution to this.
I could add another startup option, for example --nowakeup, to implement
this way of doing it. Do you think that is worthwhile?
--
Ticket URL: <https://code.mythtv.org/trac/ticket/13136#comment:2>
MythTV <http://www.mythtv.org>
MythTV Media Center
More information about the mythtv-commits
mailing list