Not logged in
Log in now
Create an account
Subscribe to LWN
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
PostgreSQL 9.3 beta: Federated databases and more
LWN.net Weekly Edition for May 9, 2013
TAI is the way to go.
Leaping seconds and looping servers
Posted Jul 4, 2012 3:28 UTC (Wed) by drag (subscriber, #31333)
As far as scientific time keeping it's already been found to be fundamentally flawed due to the fact that they didn't take the effect of gravity into it. and is probably going to be replaced by something else eventually that is adjusted for altitude.
Posted Jul 4, 2012 13:26 UTC (Wed) by andreasb (subscriber, #80258)
Posted Jul 4, 2012 18:32 UTC (Wed) by cesarb (subscriber, #6266)
GPS does. The GPS timestamp is TAI with a fixed offset.
Posted Jul 17, 2012 17:59 UTC (Tue) by Baylink (subscriber, #755)
The problem here is not the *choice of timescale*: UTC is monotonic even over leap seconds; 58, 59, 60, 00.
The *problem* is that the kernel isn't following UTC *either*; not if it's ticking backwards. It's that *ticking backwards* part that is the problem, and I've yet to see a truly compelling reason why it should do so.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds