Yup, /etc/conf.d/ntpd is the same except for the server. If I stop ntpd
and do ntpdate [the server named] I get:
MRK root # ntpdate tock.usno.navy.mil
22 Mar 14:46:00 ntpdate[20695]: adjust time server 192.5.41.41 offset
-0.002197 sec
/etc/ntp.conf is all commented except for the 3 servers below
server ntp2.usno.navy.mil iburst
server tick.usno.navy.mil iburst
server tock.usno.navy.mil iburst
ant the logfile and driftfile lines
All 3 servers are reachable with the ntpdate command
and
MRK root # ntpq -p
remote refid st t when poll reach delay offset
jitter
==============================================================================
*ntp2.usno.navy. .PSC. 1 u 10 64 37 90.429 1.822
5.673
+ntp0.usno.navy. .PSC. 1 u 4 64 37 83.955 2.160
0.046
+tock.usno.navy. .PSC. 1 u 64 64 17 85.316 1.973
0.803
I'm not so sure that I really have a problem as the clock is rarely more
than 2 miliseconds off. The drift # (-143.870) bothers me. This is near
the offset I had the first time I ran ntpdate. Seeing that the time is
essentially correct now, should I set the drift to 0 or to the ofset I
get the next time I call "ntpdate?
On Saturday 22 March 2003 02:07 pm, Mitchell James wrote:
> Did you try a different server?
> This is the two active lines from my ntpd. Everything else is
> commented out. Substitute your own server for "tick.uh.edu".
> NTPDATE_CMD="ntpdate"
> NTPDATE_OPTS="-b tick.uh.edu"
> Mitchell James
>
> Ernie Schroder wrote:
> >I read through a recent thread on ntp and I've googled around but I
> >guess I'm not asking the right questions. I think I should have ntpd
> >working. I've added servers to ntp.conf edited /etc/conf.d/ntpd and
> >generally I think I've set things up right. Can someone interpret
> > this excerpt from the /var/log/ntpd.log? this is from after my last
> > changes.
> >
> >22 Mar 09:57:52 ntpd[19412]: ntpd exiting on signal 15
> >22 Mar 09:57:53 ntpd[19574]: frequency initialized -143.872 from
> >/var/lib/misc/ntp.drift
> >22 Mar 09:57:53 ntpd[19576]: signal_no_reset: signal 17 had flags
> >4000000
> >22 Mar 09:58:37 ntpd[19574]: kernel time discipline status change 41
> >22 Mar 10:13:52 ntpd[19574]: ntpd exiting on signal 15
> >22 Mar 10:13:54 ntpd[19666]: frequency initialized -143.872 from
> >/var/lib/misc/ntp.drift
> >22 Mar 10:13:54 ntpd[19670]: signal_no_reset: signal 17 had flags
> >4000000
> >22 Mar 10:14:34 ntpd[19666]: kernel time discipline status change 41
>
> --
> [EMAIL PROTECTED] mailing list
--
Regards, Ernie
100% Microsoft and Intel free
--
[EMAIL PROTECTED] mailing list
