> The most productive action will likely be emailing the server operators to > tell them that the leap flag is wrong. Suggestions welcome, feel free to > add notes or new issues in the issue tracker: > https://github.com/abh/ntppool/issues
Agreed - wasn't it an issue with older versions of NTPD? They would announce a leap second if one or more of their sources said a leap second was due. Newer versions need at least half of their sources to say a leap second is due before they will announce it IIRC. If the server has a local "leap-seconds" file I guess it uses that in preference? Maybe an email alert to the server owner if their server is incorrectly advertising a leap second with a link to a page giving details about which versions of NTPD are affected and how to configure their server to use a local "leap-seconds" file? I've got a couple of NTPD servers and the config to use the leap-seconds file was different as they are running different versions of NTPD, so maybe we can submit our different working configs to build up a list? I also knocked up some cron scripts to automatically check for an update of the leap-seconds file and FTP it across - maybe those would be useful? Thanks, Laurence _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
