4 ms·
Your phone should update at one second before midnight UTC. So if your in EST then at 6:59:59, watch for 59 to be counted twice.
by joeax 10y ago
Your phone should update at one second before midnight UTC. So if your in EST then at 6:59:59, watch for 59 to be counted twice.
- andrewstuart2 10y agoHave our timekeeping protocols really accounted for future events like that? It's my understanding that NTP really only synchronizes time periodically.
- lmm 10y agoYour phone/computer should (according to the standard) know when the leap second is and apply it. NTP etc. transmit the information about leap seconds well in advance.
- detaro 10y agoNTP includes flags for "leap second at the end of day", so devices that check NTP time at least once a day get the information. The systems internal list of leap seconds is possibly updated before that through normal system updates.
- kqr 10y agoIt is possible your device may not see a leap second, only eventually observe that it is running one second slow, and smear to correct for that.
- gshubert17 10y agoI believe 6:59:59 will be followed by 6:59:60. See the screen shot I took of a leap second added in 2008. https://www.flickr.com/photos/127045916@N06/31678955582/ https://www.flickr.com/photos/127045916@N06/31678955582/
- devy 10y agoYep. The extra second is the 60th second. http://earthsky.org/human-world/leap-second-june-30-december-31-why-need-controversy http://earthsky.org/human-world/leap-second-june-30-december...
- op00to 10y agoThere's a bunch of ways the leap second can be reflected. :59 twice, :60, leap second smearing (adding small amounts of time leading up to midnight). How your particular system reacts depends on the use, how it's configured, etc.
- joeax 10y agoThat makes sense. I was being slightly facetious, and I think most devices would NTP re-sync after some interval. But it would be cool if my phone did in fact show 3:59:60 (I'm pacific time) and/or analog smartwatch paused on the 59 for two seconds.