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: http://ntp.isc.org/bin/view/Support/AccessRestrictions With particular attention to the following section: > 6.4.1.2. Add exceptions for specific hosts/subnets > > Once you have set your default restriction you may need to add > exceptions, in the form of additional restriction lines, to allow > your remote time servers and client hosts/subnets to contact your > ntpd. -- -Chuck _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
