TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Making every (leap) second count with our new public NTP servers

110 点作者 scommab超过 8 年前

7 条评论

liotier超过 8 年前
“Leap Smearing must not be used for public-facing NTP servers” - <a href="https:&#x2F;&#x2F;tools.ietf.org&#x2F;html&#x2F;draft-ietf-ntp-bcp-02" rel="nofollow">https:&#x2F;&#x2F;tools.ietf.org&#x2F;html&#x2F;draft-ietf-ntp-bcp-02</a>
评论 #13079451 未加载
评论 #13079081 未加载
评论 #13078013 未加载
评论 #13080350 未加载
brandmeyer超过 8 年前
&gt; Instead of adding a single extra second to the end of the day, we&#x27;ll run the clocks 0.0014% slower across the ten hours before and ten hours after the leap second, and “smear” the extra second across these twenty hours.<p>Holy leaping second, batman! Unilaterally being off by up to a half second from the rest of the world&#x27;s clocks is a pretty aggressive step. I think I would have preferred to see a resolution made by an independent body on something this drastic.
评论 #13077198 未加载
评论 #13077055 未加载
评论 #13077167 未加载
评论 #13077031 未加载
nullc超过 8 年前
I predicted this for leap smear a while back-- we have time sync because having systems with different times is a source of problems... logical fix: get them onto the same time.<p>Smear is a workaround for those who care about phase alignment but don&#x27;t care about frequency error. ... and who don&#x27;t need to exchange times with anyone else. This last point reduces the set to no one, since it can&#x27;t extend to everyone (some parties care a lot more about frequency error than phase error!).<p>This circus is enhanced by NTP&#x27;s inability to tell you what timebase it&#x27;s using (or, god forbid, offsets between what its giving you and other timebases...)<p>It&#x27;s going be especially awesome when NTP daemons with both smear and non-smear peers get both the smear frequency error AND get a leap second.<p>I for one welcome this great opportunity for an enhanced trash fire to help convince the world that we need to stop issuing leap seconds. (It&#x27;s absurd-- causes tens of millions in disruption easily, -- and it would take 4000 years to even drift an hour off solar time, at which point timezones could be rotated if anyone really cared).
评论 #13078515 未加载
leephillips超过 8 年前
A lot of interesting geophysics in the unpredictable need for leap seconds. I mention Google&#x27;s &quot;smearing&quot; approach here:<p><a href="http:&#x2F;&#x2F;arstechnica.com&#x2F;science&#x2F;2016&#x2F;04&#x2F;the-leap-second-because-our-clocks-are-more-accurate-than-the-earth&#x2F;" rel="nofollow">http:&#x2F;&#x2F;arstechnica.com&#x2F;science&#x2F;2016&#x2F;04&#x2F;the-leap-second-becau...</a>
评论 #13077519 未加载
leni536超过 8 年前
Why the hell aren&#x27;t time servers and clients sync to TAI instead? Dealing with leap seconds should be a client side problem.
评论 #13079225 未加载
评论 #13078003 未加载
评论 #13077751 未加载
评论 #13077846 未加载
antoncohen超过 8 年前
For people talking about Google unilaterally doing this, it has been common to smear the leap second for the last couple years. Usually companies do it internally by having their NTP servers skew time, either with Chrony or `ntpd -x`. Standards bodies have not been able to react quickly enough to the need to smear the leap second in a consistent way. I&#x27;m thankful that Google has decided to run public NTP servers with consistently smeared leap seconds.<p>Here are two Red Hat articles on how to deal with the leap second, from 2016 and 2015:<p><a href="https:&#x2F;&#x2F;access.redhat.com&#x2F;articles&#x2F;15145" rel="nofollow">https:&#x2F;&#x2F;access.redhat.com&#x2F;articles&#x2F;15145</a><p><a href="http:&#x2F;&#x2F;developers.redhat.com&#x2F;blog&#x2F;2015&#x2F;06&#x2F;01&#x2F;five-different-ways-handle-leap-seconds-ntp&#x2F;" rel="nofollow">http:&#x2F;&#x2F;developers.redhat.com&#x2F;blog&#x2F;2015&#x2F;06&#x2F;01&#x2F;five-different-...</a>
评论 #13083510 未加载
newman314超过 8 年前
Does anyone know if Google has open sourced the time smearing algorithm?
评论 #13078118 未加载
评论 #13078126 未加载