Re:No leap second will be added tonight
by bpicolo on Monday June 30, 2014 @11:26AM
(#7965516)
These things matter a lot for time libraries.
[ Parent
| on HN ]
It's pretty "crazy" that all software that handles UTC needs to have an access to the internet (or software updates) every 6 months. You simply can't leave, say, a sensor somewhere for a year and expect it to record events in UTC.
Sure, you can record events in something else than UTC and convert it to UTC at a later time.
Re:No leap second will be added tonight
by fennecfoxen on Monday June 30, 2014 @01:23PM
(#7966258)
Unless you have some fancy hardware around running your clock you've got bigger issues; as a general rule you can't run a computer and expect the time to remain +/- 1 second of UTC.
Re:No leap second will be added tonight
by agildehaus on Monday June 30, 2014 @02:49PM
(#7966799)
NTP exists so we don't have to own this hardware. You can easily expect to be within milliseconds of UTC if this is working properly and you're syncing with stratum 1 servers.
And better yet, the hardware to do this yourself isn't really "fancy" anymore: http://www.newegg.com/Product/Product.aspx?Item=9SIA19G0A497...
Re:No leap second will be added tonight
by Dylan16807 on Monday June 30, 2014 @03:10PM
(#7966956)
Uh, NTP needs to have access to the internet (or a specialized hardware clock).
GPS is also relying on a network.
Running a calibrated atomic clock yourself is definitely in 'fancy' territory.
Re:No leap second will be added tonight
by agildehaus on Monday June 30, 2014 @04:41PM
(#7967566)
The statement was that you needed fancy hardware to get < 1 sec accuracy to UTC which is patently false, network availability or not you can easily (without an atomic clock) get that level of accuracy.
You need fancy hardware to get that level of accuracy in any way that doesn't also automatically give you leap second announcements, which was the problem we were talking about. NTP announces them, GPS announces them, the various longwave time stations announce them...
Re:No leap second will be added tonight
by fennecfoxen on Monday June 30, 2014 @04:54PM
(#7967646)
Eh. That hardware $300 and requires a network connection too. If that's reasonable to do, is network access to distribute leap-second information really a problem?
(There may be cases where the answer is yes, but... we digress.)
Yep. That's why unixtime is actually a pretty logical measure.
Yes, they do. However, adding the second is not the default, so announcement that it's not going to be added is not as interesting. Also, I doubt "time libraries" "people" get their news from HN, on a day it could happen.
On the other hand, the HN public is one that should be acutely aware of leap second issues, because it's urgently necessary that all programmers should have some basic knowledge of this issue. So it's a good idea to draw attention to this a few times per year.
But probably not at such short notice.
Re:No leap second will be added tonight
by edwintorok on Monday June 30, 2014 @11:32AM
(#7965548)
Doesn't seem short at all: "Paris, 16 January 2014 [...] NO leap second will be introduced at the end of June 2014."
The notice was posted 6 months ago.
Re:No leap second will be added tonight
by nanofortnight on Monday June 30, 2014 @11:47AM
(#7965647)
It is standard practice to post such notices six months in advance. That's what the IERS normally does at least.