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. I have seen 4.2.6p5 fail in pool service, though.
> If the 4.2.6-4.2.8 diff was just bug fixes and nothing else, I think
> the downstream packagers would be quicker in rebasing to the new
> version. But there are incompatibilies and new bugs, known and
> unknown. Trying to force downstream packagers to rebase is not likely
> going to work.
Incompatibilities? I run a mixed-mode cluster serving time
to millions of clients running everything on the planet and haven't
run into any problems.
Can you provide some specifics about these stability and
compatibility bugs?
> How many of those >1000 bugs are actually in 4.2.6 and how many of
> them are important? To me it looks like a lot of them were bugs
> introduced in the 4.2.7 development. There are commits with unrelated
> changes mixed together, with no comments, so it may not be easy to
> determine whether something is actually a bug fix.
4.2.6 was initially released in 2009. From 2009 until the
release of 4.2.6p5 in 2011, it would only have received major bugfixes,
and security patches, and after the release of 4.2.8, nothing, as
it's not the currently supported stable release.
As far as 4.2.7 development goes, I am shocked, shocked I
say, that bugs were found and subsequently fixed in a development
branch. This sounds like normal software development work to me,
and I don't understand that portion of your complaint at all. Bugs
happen. They are part of software. As long as the critical ones
are found and fixed, I am happy.
Why fight so hard to run 6 year old software on the public
Internet?
Cheers,
--msa
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
