[mythtv-commits] Ticket #12972: Frontend idle timeout cannot be fully disabled

[MythTV]

#12972: Frontend idle timeout cannot be fully disabled
------------------------------+------------------------
 Reporter:  amb@…             |          Owner:
     Type:  Patch - Bug Fix   |         Status:  new
 Priority:  minor             |      Milestone:  29.0
Component:  MythTV - General  |        Version:  0.28.0
 Severity:  low               |     Resolution:
 Keywords:                    |  Ticket locked:  0
------------------------------+------------------------

Comment (by rsiddons):

 P Bennett is correct. This is the wrong fix.


 >> 6.b.i If they have set the configuration value to non-zero then they
 will go to standby.
 Settings aren't created in the database until they're modified, so a
 default installation would never go to standby. This could be rectified
 by:
 {{{
 GetNumSetting("FrontendIdleTimeout", 999) > 0
 }}}
 However that isn't appropriate either.

 Standby mode is used for 2 separate requirements;
 1. A frontend that has started (ie. not in standby mode) will go into
 standby when left idle. This is what the setting/documentation is
 referring to.
 2. A BE/FE that starts automatically (without !MythWelcome) must go into
 standby so that it will shutdown. The idle timeout isn't relevant here.
 The doc refers to the setting/idle function, not Standby mode.

 A user may set idle timeout to 0 to prevent Myth ever shutting down once
 they have started it. But they still need it to shutdown after automatic
 starts though.

 >> The problem is triggered if I start the frontend from mythwelcome just
 before a recording is scheduled to start when it goes to standby and I
 have to press another key to exit standby.
 This is the real issue. In fact it's worse than that because
 !WasAutomaticStart uses *within* rather than *before*: restarting the FE
 up to 15 mins after a recording has started will also put it into standby
 IIRC.

 Ideally !WasAutomaticStart could be improved for everyone. But for this
 specific case a better fix may be for it to return false if !MythWelcome
 is running (as in !BackendIsRunning)

 Out of curiosity, why do you still use !MythWelcome ? Standby is its
 preferred replacement, although there are some features that haven't been
 ported (yet). Are you using those ?

--
Ticket URL: <https://code.mythtv.org/trac/ticket/12972#comment:7>
MythTV <http://www.mythtv.org>
MythTV Media Center