On Mon, Sep 07, 2015 at 05:35:08PM -0400, Majdi S. Abbas wrote: > On Mon, Sep 07, 2015 at 11:53:51AM +0200, Miroslav Lichvar wrote: > > If everyone updated to 4.2.8 right after it was released, a large > > fraction of the pool servers would likely be down. There were (and > > apparently still are) some bugs that caused ntpd to crash on busy > > servers. > > I haven't had any stability problems, and I've been running > 4.2.8 from the time it was an RC, and 4.2.7 development releases > before that.
That's great, but there were reports (even on this list) that ntpd is crashing after update to 4.2.8. I think most users were hit by the memory locking issue, which was addressed later. > Can you provide some specifics about these stability and > compatibility bugs? Hal mentioned a bug causing crash on FreeBSD. There are reports about crashes when Autokey is enabled. An incompatibility is that the ntpdc protocol no longer supports the monlist command and also that the protocol is disabled by default now. These changes make sense and most users won't care, but admins that have a monitoring system built around ntpdc will have to do something about it. As a downstream maintainer I have to consider all these things. Updating to 4.2.8 in a new major OS relase is fine, but don't be surprised if a stable release of your favorite distro stays at 4.2.6p5. -- Miroslav Lichvar _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
