<br><br><div><span class="gmail_quote">On 10/8/07, <b class="gmail_sendername">Mike Perkins</b> <<a href="mailto:mikep@randomtraveller.org.uk">mikep@randomtraveller.org.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jerome Yuzyk wrote:<br>> I am wondering if any Myth users have been seeing clock-drift with Fedora 7. I<br>> was wondering what was going on when my evening recordings began to start<br>> noticeably late. For years I have used
<span style="font-weight: bold;">ntpdate </span>to sync my clock at 1 minute<br>> after 4am and log the result. On my Myth box pre-Fedora 7 the time difference<br>> was around 0 - usually -0.7 seconds. The day I upgraded I started logging
<br>> differences of 12 seconds, every single day. I _vaguely_remember reading<br>> something about this happening in recent kernels (when the CPU governor is<br>> used) but no amount of Googling turns up any similar references.
<br>><br>> Anyone else noticed this? I started noticing when the 11pm news started<br>> getting about 10 seconds clipped off the front.<br><br>Is<span style="font-weight: bold;"> ntpd </span>an option for you? It's what I use on all my pcs.
<br><br></blockquote></div>Or rather is running it multiple times per day an option, I also didn't find anything other than that systems with high load my loose time. One of my oldest machines has had this problem for a long time it works good for about a week with a new cmos battery and then starts loosing 2 - 5 seconds per hour. If it wasn't time sensative it would be ok, but some of it's work is time sensative so I sync the time 4 times per day.
<br><br><br>