3 ms·

what's wrong with OpenNTPD exactly?

• NelsonMinar 10y ago
  There's a summary of some of its limitations here: https://en.wikipedia.org/wiki/OpenNTPD#Criticism https://en.wikipedia.org/wiki/OpenNTPD#Criticism One of them (lack of leap second support) is fresh on our minds since we just had a leap second. Some thoughts from the OpenNTPD folks are at http://undeadly.org/cgi?action=article&sid=20150628132834 http://undeadly.org/cgi?action=article&sid=20150628132834 Chrony is another alternate NTP implementation, here's their comparison vs ntpd and openntpd. https://chrony.tuxfamily.org/comparison.html https://chrony.tuxfamily.org/comparison.html
  • elchief 10y ago
    It sounds like the leap-second thing isn't that big of an issue though...
    • NelsonMinar 10y ago
      The leap second thing is a big issue for a server. OpenNTPD serves the wrong time on the day of the leap second. They don't propagate the leap second flag properly either. It's not correct and doesn't belong in a public server pool IMHO. This issue isn't just theoretical: it was responsible for a lot of the bad time being served by the NTP Pool last week. You're right that the article I linked argues the leap second isn't a big problem to client machines. I guess I sort of believe it, if you don't care if your client is a second off from true time once every couple of years.