<br><br><div class="gmail_quote">On Thu, Oct 6, 2011 at 8:17 PM, criggie <span dir="ltr"><<a href="mailto:criggie@criggie.org.nz">criggie@criggie.org.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 06/10/11 20:37, AlanP wrote:<br>
> Is there any way to get the remote frontend to ignore the time difference<br>
> and run mythfrontend anyway (preferable)? Or to get NTP to somehow slave on<br>
> a regular basis to the backend PC?<br>
<br>
</div>Is the clock pooched, or is ntp severely confused and upsetting it?<br>
<br>
You could call<br>
ntpdate yourlocalserver<br>
every short-time, but that's a dodgy hack. Don't do it to an internet host.<br>
<br></blockquote></div><br>Definitely not. If you're running the ntp daemon, rather than just calling ntpdate every now and then, it should be keeping your clock in sync and storing drift information?<br>