<br><br><div class="gmail_quote">On Mon, Dec 3, 2012 at 8:05 AM, Robert M. Riches Jr. <span dir="ltr"><<a href="mailto:rm.riches@jacob21819.net" target="_blank">rm.riches@jacob21819.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ever since the change back from DST back to standard time, Myth<br>
has been recording scheduled shows an hour late. After seeing<br>
(most of) the discussion about how Myth uses UTC internally for<br>
scheduling,</blockquote><div><br>Not on your version it doesn't, that change came in 0.26.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I would have thought the situation would fix itself<br>
after a couple of weeks. Fortunately, I have a manual recording<br>
of the same time-slot, and that is working fine. This is on a<br>
system that runs 24x7 and has 70 days of uptime. </blockquote><div><br>Sorry about your uptime, but I think a reboot may sort this.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The shows in<br>
question are OTA from a local station. The system is 0.24.1 on<br>
Mageia 1. (Yes, I'm moving to Mageia 2 as quickly as possible.)<br>
<br>
Will Myth eventually run out of DST-based program guide info<br>
and start/resume recording the shows at the right time?<br>
<br>
If not, what must be done to shock Myth into figuring out what<br>
time it really is? Is it sufficient to restart mythbackend?<br>
Or, is there additional remedial action needed--just because of<br>
a change from DST back to standard time?<br>
<br>
Thanks,<br>
<br>
Robert<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</blockquote></div><br>