Re: sntpclock: warning: unable to read clock: timed out
Teh Kok How <[email protected]> Tue, 12 Nov 2002 10:04:19 +0000
| Newsgroups | gmane.comp.lib.libtai |
|---|---|
| Organization | Willowglen MSC Berhad |
| Message-ID | <[email protected]> |
Hi, The ntp server is reachable as shown below: [khteh-pc src 44 ]> sntpclock 192.168.80.7 | clockview before: 2002-11-12 10:03:07.636972000000000000 after: 2002-11-12 02:02:25.989040499896623193 [khteh-pc src 45 ]> Any comment and suggestion is appreciated. Regards, TEH On Tuesday 12 November 2002 01:35, you wrote: > On Tue, Nov 12, 2002 at 09:26:30AM +0000, Teh Kok How wrote: > > I have dowloaded the clockspeed-0.62.tar.gz recently and have > > installed it on my Pentium machine running OpenBSD 3.1. Unfortunately I > > encounter errors as shown below: > > > > [khteh-pc khteh 5 ]> sntpclock 192.168.80.7>/usr/local/clockspeed/adjust& > > [2] 4374 > > [khteh-pc khteh 6 ]> sntpclock: warning: unable to read clock: timed out > > sntpclock: warning: unable to read clock: timed out > > sntpclock: warning: unable to read clock: timed out > > sntpclock: warning: unable to read clock: timed out > > sntpclock: warning: unable to read clock: timed out > > sntpclock: warning: unable to read clock: timed out > > sntpclock: warning: unable to read clock: timed out > > sntpclock: warning: unable to read clock: timed out > > sntpclock: warning: unable to read clock: timed out > > sntpclock: warning: unable to read clock: timed out > > sntpclock: fatal: time uncertainty too large > > It could be that 192.168.80.7 isn't running an NTP server, or if it is it's > for some reason unreachable from your computer. > > Chris