* Phil Pennock <[email protected]> [2012-03-02 16:32]: > A brief skim of the source (4.6p1) suggests that OpenNTPd passes on
well, 4.6 is ancient. unfortunately nobody maintains the portable atm. that said, otoh there we no changes regarding leap seconds afterwards. > leap-second indicators found from servers but otherwise does nothing > with them; in particular, the local clock is never adjusted as a result > of leap-seconds, until after the event when the upstream servers pass on > the new value of time and OpenNTPd corrects time accordingly, as though > the local system were just a second fast (which it literally now is). > > Is this correct? If not, can someone aim the cluebat appropriately to > point me to what I've missed, please? it's been a while that I've been in there but if memory serves your observation is correct. > Is this "correct it afterwards as though fast" approach the planned > behaviour, or merely a result of nobody getting around to implementing > something better? more of the latter then the former. > Is there likely to be a release changing the behaviour before July 1st? no. -- Henning Brauer, [email protected], [email protected] BS Web Services, http://bsws.de, Full-Service ISP Secure Hosting, Mail and DNS Services. Dedicated Servers, Root to Fully Managed Henning Brauer Consulting, http://henningbrauer.com/
