[mythtv-commits] Ticket #12293: mythfilldatabase running on suggested time even though disabled
MythTV
noreply at mythtv.org
Fri Dec 12 18:30:06 UTC 2014
#12293: mythfilldatabase running on suggested time even though disabled
---------------------------------------+------------------------------
Reporter: jan@… | Owner: stuartm
Type: Bug Report - General | Status: closed
Priority: minor | Milestone: unknown
Component: MythTV - Mythfilldatabase | Version: 0.27-fixes
Severity: medium | Resolution: Works for me
Keywords: | Ticket locked: 0
---------------------------------------+------------------------------
Comment (by Jan Schneider <jan@…>):
Only that those contraints do not work. Or maybe they don't work as
expected. Here are my relevant settings:
MythFillDatabaseArgs: -v xmltv --syslog local7 -- --days 20
mythfilldatabaseLastRunEnd: 2014-12-11T19:50:34Z
mythfilldatabaseLastRunStart: 2014-12-11T18:50:26Z
MythFillGrabberSuggestsTime: 0
MythFillMaxHour: 19
MythFillMinHour: 17
Now, reviewing these settings again, I think I may have found the culprit:
any chance that the contraints now have to be specified in UTC instead of
local time?
Besides that the settings should have been converted when switching to
all-things-UTC a while ago, I still thing using UTC doesn't make any sense
here. IMO the setting only makes sense to schedule the update for less
crowded times. Be it crowded times on the EPG providers backends or
crowded times in front of the TV when you don't want to lose WAF or CAF
from EPG update interruptions. And then there's of course still the
reasoning from above, having the schedule updated before prime time
starts.
But for any of those scenarios, UTC doesn't make any sense, only local
time makes sense. And local time will change due to DST if these values
are specified in UTC.
--
Ticket URL: <https://code.mythtv.org/trac/ticket/12293#comment:6>
MythTV <http://www.mythtv.org>
MythTV Media Center
More information about the mythtv-commits
mailing list