On Sun, Dec 12, 1999 at 01:40:54PM -0500, Darxus wrote:
On Sun, 12 Dec 1999, Mirek Kwasniak wrote:
I used your short list as above:
# ntpdate -v `cat /tmp/clock.lst`
12 Dec 10:55:42 ntpdate[1174]: ntpdate 4.0.98f Sun Nov 21 00:35:29 MST 1999
(1)
12 Dec 10:55:47 ntpdate[1174]:
On Mon, 13 Dec 1999, Mirek Kwasniak wrote:
Try ntpq, is it working?
ntpq does work. Does ntpdate use (a) port(s) that ntpq doesn't, so maybe
my ISP might have started blocking something ?
No, both ntpdate ntpq use ntp udp port.
Again:
- to long (99) servers list
- temporary
]: no server suitable for synchronization
found
# wc -l clock.lst
99 clock.lst
# head clock.lst
129.127.28.4
129.132.98.11
193.2.69.11
128.173.14.71
193.136.54.1
128.100.102.201
128.118.25.3
130.228.230.2
194.192.207.9
192.48.153.74
Nov 21 00:35:29 MST
1999 (1)
11 Dec 22:43:28 ntpdate[28516]: no server suitable for synchronization
found
# wc -l clock.lst
99 clock.lst
# head clock.lst
129.127.28.4
129.132.98.11
193.2.69.11
128.173.14.71
193.136.54.1
128.100.102.201
128.118.25.3
130.228.230.2
194.192.207.9
On Sat, 11 Dec 1999, Darxus wrote:
ntp hasn't seemed to work for me for a while. I figured maybe all the ntp
servers I'd set it to use nolonger ran the ntp server or something. But I
just pulled 99 servers off of a list at http://www.eecis.udel.edu/~ntp/
(1st relavant hit on ntp on
On Sun, 12 Dec 1999, Mirek Kwasniak wrote:
I used your short list as above:
# ntpdate -v `cat /tmp/clock.lst`
12 Dec 10:55:42 ntpdate[1174]: ntpdate 4.0.98f Sun Nov 21 00:35:29 MST 1999
(1)
12 Dec 10:55:47 ntpdate[1174]: adjust time server 129.132.98.11 offset
-0.000396 sec
Maybe
6 matches
Mail list logo
