ntpdate and Ultra 5
Hi,
It has been suggested previuosly that when rtc cannot be accessed properly
on an ultra5 to use ntpdate to set system time.
This is the output of ntpdate -d
12 Nov 11:06:55 ntpdate[372]: ntpdate 4.1.0 Thu Mar 28 10:32:38 UTC 2002 (2)
transmit(192.168.1.25)
receive(192.168.1.25)
transmit(192.168.1.25)
receive(192.168.1.25)
transmit(192.168.1.25)
receive(192.168.1.25)
transmit(192.168.1.25)
receive(192.168.1.25)
transmit(192.168.1.25)
server 192.168.1.25, port 123
stratum 11, precision -17, leap 00, trust 000
refid [127.127.1.0], delay 0.02612, dispersion 0.00000
transmitted 4, in filter 4
reference time: c19347ae.c4f17000 Sat, Nov 30 2002 14:20:30.769
originate timestamp: c19347cf.6ccf8000 Sat, Nov 30 2002 14:21:03.425
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
transmit timestamp: 419347cf.6d07b784 Mon, Nov 12 1934 11:06:55.425
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
filter delay: 0.02634 0.02614 0.02612 0.02612
0.00000 0.00000 0.00000 0.00000
filter offset: -0.00111 -0.00116 -0.00116 -0.00116
0.000000 0.000000 0.000000 0.000000
delay 0.02612, dispersion 0.00000
offset -0.001163
12 Nov 11:06:55 ntpdate[372]: adjust time server 192.168.1.25 offset -0.001163 sec
The ntp server is running RH6.2 sparc updated with rh kernel 2.2.22 and
about ten other machines (solaris, netbsd, linux, NT) get the time
correctly from this server.
The ultra 5 is running woody 3.0 updated with a 2.4.19 deb kernel.
Any help will be appreciated.
--
Regards,
Antonio Prioglio [a.prioglio@cbtcentre.co.uk]
http://www.cbtcentre.co.uk
====================================================
Cognitive Behavioural Therapy Centre - London
Reply to: