Re: Problems with NTPD

["MikeM" <myraq_(_at_)_mgm51_(_dot_)_com>]

On 1/6/03 at 7:30 AM auto470779_(_at_)_hushmail_(_dot_)_com wrote:

|/etc/rc.conf contains:
|
|ntpdate_flags="ntp0.fau.de"


   ntpdate_flags="-sv ntp0.fau.de"

will give you a little more info in your syslog file.




|/var/log/ntpd.log contains: 
|
| 6 Jan 15:24:57 ntpd[2615]: ntpd exiting on signal 15
| 6 Jan 15:26:29 ntpd[20212]: Un-parsable frequency in /etc/ntp.drift

I typically see the un-parsable frequency message when started up a new
installation of ntpd.  Leave it alone for a few hours and the ntpd daemon
will put a number in the file it likes. 

But I'm a little concerned about the signal 15 message.  It's a different
process number, so it may not be related to the un-parsable frequency
message that occurs a couple of minute slater.


If you run the command   

   /usr/local/sbin/ntpq -c peer

what does the output look like?  Here's mine:

# /usr/local/sbin/ntpq -c peer
     remote           refid      st t when poll reach   delay   offset
jitter
============================================================================
==
+ns1.ct.thebiz.n bonehed.lcs.mit  2 u  106 1024  377   20.451   -4.040
0.233
*filbert.cc.colu gnomon.cc.colum  2 u   70 1024  377   58.086    3.982
1.735
+cudns.cit.corne ntp2.usno.navy.  2 u  191 1024  377   38.936   -8.559
0.797