4 ms·
Not wanting to be a complete BSD bigot, I can't actually remember if this broke in the {Free,Net,Open}BSD world as badly. The 2015 docs for FreeBSD don't help (
by ggm 8y ago
Not wanting to be a complete BSD bigot, I can't actually remember if this broke in the {Free,Net,Open}BSD world as badly. The 2015 docs for FreeBSD don't help (oh, for a time machine) but go to "you can test what we do" which is good.
https://www.freebsd.org/doc/en_US.ISO8859-1/articles/leap-seconds/article.html https://www.freebsd.org/doc/en_US.ISO8859-1/articles/leap-se...
- ajross 8y agoNot to jump on the bigotry, but two of the three bugs mentioned in that comment were in proprietary software (Java and RRDNS) that merely runs on Linux. The hrtimer issue in 2012 was a real kernel bug though.
- repolfx 8y agoJava was open sourced in 2006.
- NelsonMinar 8y agoThe 2012 bug was a bad interaction between Java and thread locking in the Linux kernel. It affected MySQL as well. The 2009 bug was in the Linux kernel, in the logging code. The 2016 bug I mentioned was in Cloudflare's proprietary code and only had a big impact because so many websites use Cloudflare. There are zillions of other smaller leap second related bugs, these are only three of the most visible. (btw, the word "bigotry" has a real meaning and this isn't it.)
- ars 8y agoBSD is actually worse, it doesn't handle leap seconds at all, it simply ignores their existence and assumes the clock was simply inaccurate. That's fine as far as it goes, but make sure never to use a BSD machine as an NTP server or you will cause a lot of confusion for any servers downstream.
- swills 8y agoI don't know about OpenBSD or NetBSD but I've witnessed FreeBSD handling leap second correctly. I also witnessed OpenNTPD ignoring it and that's documented, so I suspect OpenBSD doesn't handle leap seconds at all.
- JdeBP 8y agoThere's more on this at https://news.ycombinator.com/item?id=18039595 https://news.ycombinator.com/item?id=18039595 .