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

MythTV noreply at mythtv.org
Fri Aug 18 19:45:03 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:11 rsiddons]:
 > Replying to [comment:9 pbennett]:


 > I agree there's a (minor) issue of sometimes incorrectly starting up in
 Standby when invoked by !MythWelcome. Its purpose is to prevent the FE
 starting up during automatic recordings. So a FE starting under
 !MythWelcome is always a manual start and !WasAutomaticStart is redundant
 in that case. IMO an explicit check is simple, clear and can easily be
 removed if/when !MythWelcome is retired.

 Provided that starting !MythFrontEnd **by any method** at the "wrong time"
 to trigger the automatic startup test doesn't automatically go to standby
 I don't care how it is done.  Checking whether it was started from
 !MythWelcome is not sufficient because if mythbackend is left always
 running and mythfrontend is started manually at the "wrong time" it will
 go to standby.

 > I'm also confused by the other comments. The OP needs to clarify:
 > 1. what other issues they are experiencing

 The only issue I have is the frontend going to standby when started even
 though the !FrontendIdleTimeout has been deliberately set to zero (which
 the documentation string tells me prevents it ever going to standby).

 > 2. what they are trying to achieve

 As for 1 above.

 > 3. why they are trying to use (abuse?) the "!FrontendIdleTimeout"
 setting to control startup behaviour.

 The !FrontendIdleTimeout controls when the frontend goes to standby, this
 is it's only purpose.  Therefore every possible place in the software that
 could go to standby must check this setting otherwise the frontend could
 go to standby when forbidden by the setting.

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


More information about the mythtv-commits mailing list