Hmmmm. "man hwclock" gives some great info of how clocks work in Linux
(I hope it is correct!) In particular, the system clock, which is a
software clock maintained by the kernel, is only loaded from the
hardware clock at bootup (unless you have some wacky script doing
"hwclock --hwtosys").
If your running xntpd, which syncs the system clock with NTP, it will
try to update the hwclock every 11 minutes, as well as updating
/etc/drift which indicates to the kernel when it boots how far to adjust
the system clock.
I would suggest to do some logging to see if you can figure out when the
drifting is occuring
For instance:
[EMAIL PROTECTED]:/usr/share/doc/ntp$ perl -e 'while(1) { print `hwclock`;
sleep 1 }'
Wed 03 May 2006 18:38:33 EST -0.988257 seconds
Wed 03 May 2006 18:38:35 EST -0.989062 seconds
Wed 03 May 2006 18:38:37 EST -0.987477 seconds
Wed 03 May 2006 18:38:39 EST -0.967914 seconds
You can also tell xntpd to do a lot more logging.
Martin Visser
Technology Consultant
Consulting & Integration
Technology Solutions Group - HP Services
410 Concord Road
Rhodes NSW 2138
Australia
Mobile: +61-411-254-513
Fax: +61-2-9022-1800
E-mail: martin.visserAThp.com
This email (including any attachments) is intended only for the use of
the individual or entity named above and may contain information that is
confidential, proprietary or privileged. If you are not the intended
recipient, please notify HP immediately by return email and then delete
the email, destroy any printed copy and do not disclose or use the
information in it.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Christopher Vance
Sent: Wednesday, 3 May 2006 4:56 PM
To: SLUG
Subject: Re: [SLUG] NTP problems
On Wed, May 03, 2006 at 02:23:42PM +1000, Julio Cesar Ody wrote:
># ntpq -p
> remote refid st t when poll reach delay offset
> jitter
>=======================================================================
=======
>*hostname 220.233.180.218 3 u 65 64 377 0.151
5.983
>0.498
What, only one host? Some say it's best to synchronize with at least
three, where each of them have independent lower stratum sources. If
your upstream ISP provides a server, use that as well as some of the
pool ones.
But to answer your question, some kernels have problems on some
motherboards.
--
Christopher Vance
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
