I'm sure it is better to have more than one. But I'm not too worry about it as these desktops will always be in the same LAN as "hostname". If hostname can't reach au.pool.ntp.org, that means the others can't as well (it actually means there's no internet connection). So no point in having multiple in this scenario.
I got notice now that the machine in question was running Fedora Core 4 with no clock problems. I reckon this has to be related with the kernel version then. I'll try replacing it and see what happens. Greg: thanks for the link. It seems the guy did a kernel upgrade and the problem vanished. I'll do the same and see what happens. On 5/3/06, Christopher Vance <[EMAIL PROTECTED]> wrote:
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
-- Julio C. Ody http://rootshell.be/~julioody -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
