On 2006-12-16 16:03, John Andersen wrote:
On Saturday 16 December 2006 06:21, ByteEnable wrote:
4 Dec 22:26:39 ntpd[12811]: synchronized to 128.138.140.44, stratum 1 14 Dec 22:26:37 ntpd[12811]: time reset -1.472229 s 14 Dec 22:26:37 ntpd[12811]: kernel time sync enabled 0001 14 Dec 22:28:18 ntpd[12811]: synchronized to 128.138.140.44, stratum 1 14 Dec 22:29:07 ntpd[12811]: no servers reachable 14 Dec 22:29:45 ntpd[12811]: synchronized to 129.6.15.29, stratum 1 14 Dec 22:30:24 ntpd[12811]: no servers reachable 14 Dec 22:30:33 ntpd[12811]: synchronized to 128.138.140.44, stratum 1
I'd be pretty suspicious of those "no servers reachable" messages.
Do you have one or several servers configured? You should use as many as 4 or 5, and <dons flamesuit> avoid the pools because they have proven to be a single point of failure IMHO. If you use a pool, make sure you have at least two other clocks named explicitly.
Universities (at least many of them in the US) seem to have time servers and mega-bandwidth. I use their servers a lot.
Both those IPs resolve; 128.138.140.44 is UColorado, while 129.6.15.29 is time-b.nist.gov. AFAIK, neither of those is in any ntp pool. The "no servers reachable" messages don't bother me very much, as ntpd should be able to keep the time within reason for a lot longer than the interval in the above log fragment. What is of more concern is that the local clock seems way out of touch with reality. That suggests to me that ntp is working properly, so long as it can reach a server of course. It is rather something in the kernel configuration that is wrong. For Byte: what is the output of "adjtimex -p"? -- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org