Terje Mathisen wrote:
OK, so exactly as encoded in the "right" zone info, there is no leap second until the table is updated/patched.
And yet there is no expiration date in the TZDB's leap second file (which is also used for the "right" time zones), so you don't know if there is no upcoming leap second, or if the table has just not been updated.
AFAIK there's some code in the git version of TZDB, though, so this may be available in future releases of TZDB.
The remaining questions is how clients (glibc using a "right" zone, or PHK's new NTP client software) can determine this is available, and use it.
Martin -- Martin Burnicki Meinberg Funkuhren Bad Pyrmont Germany _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
