Chuck Swiger wrote: > On Dec 4, 2006, at 11:24 AM, Kim B. Sindalsen wrote: > [ ... ] >> I’ve recently set up a ntp-server (ntp.vlh.dk) and added it to the >> pool and beside an alarming offset of about 400ms recently (http:// >> stats.vlh.dk) it seems to be working quite well. >> >> Now I’ve then started collecting some stats using the script found >> here: http://www.schlitt.net/scripts/ntp/ >> >> This revealed something that I surely didn’t expect to see. >> >> The server itself (10.0.1.1) is listed as the top-requesting >> client, producing about 25% of the total requests – I’m sure that’s >> not meant to be so, or am I wrong? > > The ntp.conf you are using most likely prevents any of the NTP > servers you have configured from adjusting your clock, and even > prevents localhost or 10.0.1.1 from making changes. Please read the > section on configuring access restrictions here:
I don't think that's it. I'm seeing a similar situation using Wayne's scripts, and I don't have any restrict lines at all in my ntp.conf. John _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
