ntp debugging output
Joel Hammer
joel
Mon May 17 12:00:47 PDT 2004
Well, despite no debugging I think I have gotten this time
thing fixed. I had this entry (put there by the debian
package manager) in my /etc/ntpd.conf on the bad machine:
server localhost
Now, in my properly working firewall ntp server there is
also this:
fudge localhost stratum 7
which fools the server into thinking that the local host is way down the
list.
On the bad machine,
ntpdc> peers
showed that the local host was a zero stratum
server. Adding that fudge line didn't change anything,
either. So, I took out the server localhost, and now my
client properly synchronizes with the firewall ntp server.
So, I guess the hardware clock on the bad machine must be
off by ten seconds a day or something.
BTW, while doing this fix I also upgraded the ntp server
on the firewall from xntp to ntp 4x and also added a
second time server in the bad client's ntp.conf, but,
I think the crucial step was getting rid of localhost.
Joel
More information about the Linux-users
mailing list