On Wed, Jun 27, 2012 at 12:35 UTC, Thomas Rieschl wrote: > but what's more interesting.. how can I ensure that my pool servers will be > working correctly? > is it sufficient to use 4.2.6 (package from debian squeeze) and configure > the "leapfile" directive?
Yes. > do I have to change the "restrict" directive to > allow querying of the leapsec? No, the leapsec variable allows you to know the leapfile was loaded properly before the last day of the month, when leap=00 will change to leap=01. Unlike the leapsec= value, the leap= value is part of every NTP response your server provides clients. leap 11 indicates your ntpd has not yet synchronized. leap 00 means synchronized with no leap second insertion/deletion at the end of the day. 10 would be the so-far-unseen deletion of a leap second. 01 means insert a leap second at the end of the day UTC. Older ntpd clients will set leap=01 themselves when any one of their upstream ntpd sources have it. 4.2.6 and newer set leap based on a vote of upstream servers, lacking a leapfile. As long as half or more of the upstream servers are flagging an insertion, so will the client ntpd. Cheers, Dave Hart _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
