[LEAPSECS] Crunching Bulletin B numbers (POSIX time)

Ian Batten igb at batten.eu.org
Sat Feb 19 18:25:45 EST 2011


> to do this correctly for ten years, it would need a ten year leap

> second table.

Or someone to supply a manual update every two or three years. If the
machine is so isolated that it cannot receive those updates, why does
the high-precision timestamp in the logs matter? This is what I fail
to see: systems which are so isolated from timekeeping hat they cannot
receive one-bit updates, and yet are so tied into timekeeping that
they need to generate and store timestamps to high precision. What's
the use case? Not some hypothetical, but a real application?


More information about the LEAPSECS mailing list