Yes, sorta. Since last week[1] the system is tracking the information.
There's an open todo to do the work to track the correct information and email operators when their server is wrong. Until I have more data I don't think it is useful to kick out servers who have it wrong as by the time we know I expect that it's too late to help most(?) clients anyway... Ask [1] https://github.com/abh/ntppool/commit/a2be3420c626ccf150006e85bf7fd7af6fe7c090 — http://askask.com/ On Mon, Jan 5, 2015 at 8:13 PM, Philip Gladstone <[email protected]> wrote: > On 1/5/15 09:01, Martin Radford wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi all, >> >> There will be a leap second at the end of June 2015.... >> >> http://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat >> >> > Excellent. My custom GPS synchronized server should pick it up > automatically (though this code is rather untested as of yet). > By the way, does the pool monitoring verify the status of the pending > leap second bits? > Philip > _______________________________________________ > pool mailing list > [email protected] > http://lists.ntp.org/listinfo/pool _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
