Re: Dual-core system will not create NTP peers
Keep the replies on the list.
On Wed, Feb 20, 2008 at 04:54:43AM -0600, Moshe Yudkowsky wrote:
> Running the system overnight, and doing an ntpdate every five minutes, I
> notice that I very consistently take a +7.5s offset -- seems like
> exactly 2.5% to the limit of my ability to measure.
>
> So the system clock runs 2.5% slow.. what could that mean?
Don't know.
Why do you run ntpdate?
The ntp docs say that ntpdate will be removed soon since ntp has a -q
option that works better.
Why not just run ntp continuously?
--
Do you have more than one computer turned on locally? What type of
internet connection do you have? If the internet is only inermittant,
you could set up a local ntp server (if its clock is more reliable).
Or, if you happen to have a GPS, you could set that up as a time source.
I don't understand why the rtc can be (or is) a problem on the amd64
boards; its a major pain in the butt. My old 486 has a very accurate
clock, being off only about 1 second per week. Whenever I have it on my
network (as in, not on-the-shelf spare), I use it as a time server when
my dial-up isn't dialed-up.
Doug.
Reply to: