OpenNTPd howto?
Bill Moran
wmoran at potentialtech.com
Tue Jul 1 17:23:01 UTC 2008
In response to B. Cook <bcook at poughkeepsieschools.org>:
> Hello All,
>
> Not sure what I am missing, but I am.
>
> so I put openntpd on a machine (10.20.0.16)
>
> cat ntpd.conf | egrep -v ^#
>
> listen on 0.0.0.0
> server clock.nyc.he.net
>
> then start it and it looks like it does:
>
> USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN
> ADDRESS
> _ntp ntpd 15751 4 udp4 10.20.0.16:55180
> 209.51.161.238:123
> _ntp ntpd 15751 6 udp4 *:123 *:*
>
>
> Strange thing one:
>
> root at core [/usr/local/etc]# 30 > ntpdate -b clock.nyc.he.net
> 1 Jul 12:43:52 ntpdate[48881]: the NTP socket is in use, exiting
>
> root at core [/usr/local/etc]# 31 > /usr/local/etc/rc.d/openntpd stop
> Stopping openntpd.
>
> root at core [/usr/local/etc]# 32 > ntpdate -b clock.nyc.he.net
> 1 Jul 12:49:57 ntpdate[70917]: step time server 209.51.161.238
> offset 358.732506 sec
>
> Why when it was running did it not update the clock on the server?
It was working on it. You should read up on NTP a bit so you understand
how it works. NTP does not "set" the clock unless you explicitly tell
it to (I believe the -s switch in openntpd). Instead, it speeds up or
slows down the clock to bring it into adjustment, which prevents software
from seeing a sudden and space-time fabric-ripping shift in time.
If you let openntpd run for a while, possibly a few hours, you'd see the
time come in to sync.
> From a different computer I can not get the time from the server
> running openntpd.
What error do you get? Run ntpdate -d on the other computer to see _why_
it's refusing to sync. I would guess it's because the OpenNTPd server
knows that it's not in sync yet, and thus refuses to sync other machines.
--
Bill Moran
http://www.potentialtech.com
More information about the freebsd-questions
mailing list