Hello, In the unlikely event one day the deletion of a leap second does happen, the loading of a NIST leapseconds file containing a negative leap second would fail. Example minimal test leapseconds file with negative leap this evening is included (TAI going from 9 to 8). At startup the NTP daemon exits with a syslog error:
| crypto_tai: leapseconds file ntpkey_leap error -1 Looking at the code, the parsing would be easy to make negative compliant, but for one point: Interoperability issues with the Autokey LEAP packet. ---- >8 ---- leap-seconds.negative-leap-test.3331411200 ---- >8 ---- # Last Update of leap second values: 27 July 2005 #$ 3331411200 # Updated through IERS Bulletin C30-negative-leap-test # File expires on: 2 January 2006 #@ 3345148800 3345062400 8 # 1 January 2006 #h 8d6045d4 d5dce07a 6cc323b0 438ab6f4 1a10b72d -------------------- >8 -------------------- >8 -------------------- Serge. -- Serge point Bets arobase laposte point net _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
