Jack Hyde wrote:
The clock drift sounds like it's probably the cause of my woes. The clocks
are normally synced to the same ntp server but I just discovered that the
ntp process wasn't being launched because the service name changed after an
update and I never added it to the default run level. The difference that
had accumulated was 12 seconds, which might be the reason why I keep getting
screwed. I fixed the problem, and will see what happens with the next bunch
of recordings.
Fixing the service was the solution I realize so just take this
as an inconsequential suggestion. I have one host chime off three
external clocks then have my other internal hosts chime off of
that. This way I'm not abusing the free to the public servers
and my local machines have a better chance of being in sync with
each other.
-- bjm
_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
