[checked archives, FAQ, website, etc] There's a leap-second on July 1st and I'm not seeing any equivalent configuration for OpenNTPd to the reference implementation's "leapfile" directive, to use a distributed leap-seconds file to let ntpd know of the leapseconds epoch rollover.
A brief skim of the source (4.6p1) suggests that OpenNTPd passes on 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? Is this "correct it afterwards as though fast" approach the planned behaviour, or merely a result of nobody getting around to implementing something better? Is there likely to be a release changing the behaviour before July 1st? Thanks, -Phil
