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

MythTV noreply at mythtv.org
Thu Aug 17 23:08:24 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 rsiddons):

 Replying to [comment:9 pbennett]:
 > I don't think that this is needed, I think all that is needed it to
 change the default in your original patch so that it uses STANDBY_TIMEOUT
 as the default if frontend idle timeout does not exist.
 STANDBY_TIMEOUT is a macro defined in a different unit so it would have to
 be duplicated. Actually the default value is irrelevant - the setting is
 only being used as a "Allow Standby on startup" flag so why not use the
 traditional 1 ?

 Users that currently set it to 0 because they never want the FE to time-
 out whilst in use would be forced to start using the max timeout to retain
 the ability of shutdown after automatic recordings. Or go back to using
 !MythWelcome. So the setting documentation
 https://www.mythtv.org/wiki/Configuring_Frontend#Shutdown.2FReboot_Settings
 requires changing as well...

 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.

 I'm also confused by the other comments. The OP needs to clarify:
 1. what other issues they are experiencing
 2. what they are trying to achieve
 3. why they are trying to use (abuse?) the "!FrontendIdleTimeout" setting
 to control startup behaviour.

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


More information about the mythtv-commits mailing list