4.8-RELEASE-p13 -and- ntpd
nw1
network101 at covad.net
Thu Oct 9 23:54:59 PDT 2003
After reading further, we've retired ntpdate from this network. Our issue may have been
the order in which we ran ntpdate and xntpd within /etc/rc.conf ; subsequently (post
reboot) immediately trying to run 'ntpdate xxx.xxx.x.x' would fail (as we posted on
http://69.3.136.141/freebsd/ntpd/ntpd_issue-1.txt).
We're not going to break it again in order to find out what went wrong. We are now
'ntpdate' *free*. We invite any and everyone else to do the same -- voluntarily retire
'ntpdate'.
Thanks for your feedback.
----- Original Message -----
From: "Lowell Gilbert" <freebsd-questions-local at be-well.ilk.org>
To: "nw1" <network101 at covad.net>
Cc: <freebsd-questions at freebsd.org>
Sent: Thursday, October 09, 2003 8:52 AM
Subject: Re: 4.8-RELEASE-p13 -and- ntpd
> "nw1" <network101 at covad.net> writes:
>
> > Our ntpd host syncs with the external public servers, but our local clients, using
ntpdate
> > to sync with the ntpd host (on the same sub-net), fails. Using ntpdate from the same
> > local clients to any external public time-server works without problems.
> >
> > The details are posted at: http://69.3.136.141/freebsd/ntpd/ntpd_issue-1.txt
>
> I don't see anyting wrong there.
>
> The next step is to see whether the packets are hitting the wire, and
> whether responses get back. You'll need to sniff the link.
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>
More information about the freebsd-questions
mailing list