[mythtv-commits] Ticket #12972: Frontend idle timeout cannot be fully disabled
MythTV
noreply at mythtv.org
Fri Aug 18 20:14:17 UTC 2017
#12972: Frontend idle timeout cannot be fully disabled
------------------------------+--------------------------
Reporter: amb@… | Owner: pbennett
Type: Patch - Bug Fix | Status: assigned
Priority: minor | Milestone: 29.0
Component: MythTV - General | Version: 0.28.0
Severity: low | Resolution:
Keywords: | Ticket locked: 0
------------------------------+--------------------------
Comment (by amb@…):
Replying to [comment:9 pbennett]:
> Replying to [comment:8 amb@…]:
> > The problem with the patch, which hasn't been fully explained above,
is that the **backend** also has an automatic startup test. If the
backend was started automatically and the frontend hasn't connected then
it will be allowed to go to sleep after the recording //even if the idle
timeout is zero//. The patch will not make the frontend go to standby so
it will connect to the backend and cancel the idle timeout for the special
case.
> I am not with you here - if the backend idle timeout is zero then it
never goes to sleep, it is on 24x7.
> > This problem only exists if the backend's idle timeout is set to zero.
If this is not the case then when the machine is started so that a
recording can be performed the frontend will go to standby after 90
minutes (or the value of !FrontendIdleTimeout if set) anyway and the
backend will allow shutdown after its own timeout.
> As I said above, if the backend idle timeout is zero it never goes to
sleep.
I thought that if the backend idle timeout is zero and it is woken by a
recording starting then it will record and then sleep again. Everything I
wrote about the backend idle timeout was based on this premise.
If I'm wrong then I apologise for the confusion that my comments on this
setting created.
--
Ticket URL: <https://code.mythtv.org/trac/ticket/12972#comment:14>
MythTV <http://www.mythtv.org>
MythTV Media Center
More information about the mythtv-commits
mailing list