Re: ntpdate issue ....

[christos%astron.com@localhost (Christos Zoulas)]

In article <55203B5E.2080502%hiwaay.net@localhost>,
William A. Mahaffey III <wam%hiwaay.net@localhost> wrote:
>
>
>.... I use a combination of ntpdate & adjtime to maintain time on my 
>LAN. Here is output from my incumbent time server:
>
>
>[root@athloncube:/etc, Sat Apr 04, 02:21 PM] 1002 # ntpdate -q 
>fly.hiwaay.net | awk '{printf $6 " "}'
>-374.785763, time [root@athloncube:/etc, Sat Apr 04, 02:21 PM] 1002 # 
>uname -a
>Linux athloncube 2.6.35.14-106.fc14.x86_64 #1 SMP Wed Nov 23 13:07:52 
>UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
>[root@athloncube:/etc, Sat Apr 04, 02:23 PM] 1003 #
>
>& from my RPi, hopefully soon to replace the incumbent:
>
>rpi # date
>Sat Apr  4 14:30:17 UTC 2015
>rpi # ntpdate -q fly.hiwaay.net | awk '{printf $6 " "}'
>17326.729876, time rpi #
>rpi # date
>Sat Apr  4 14:30:31 UTC 2015
>rpi # uname -a
>NetBSD rpi 7.0_BETA NetBSD 7.0_BETA (RPI.201503272230Z) evbarm
>rpi #
>
>i.e. the value provided by ntpdate on the RPi looks wrong to me. The 
>-375-ish sec. value from the incumbent is correct.  Please advise & do 
>not hesitate to ask for any more info req'd. TIA & keep up the good work.

Why don't you run ntpd?

christos