prep for cutting a release, target 2019-01-13

[Eric S. Raymond]

Achim Gratz via devel <devel at ntpsec.org>:
> So again, a rate_exceeded event is logged and hpoll has moved up to 10.
> Note that both ntpq and ntpmon show the poll interval still as 16s and
> full reachability, which isn't true.  Also, looking at the peer stats
> you'll see that the effective poll interval actually changes once in a
> while.  1024s is slightly above 17 minutes, but the distance betwee
> successful pols that get recorded in peerstats is often larger than
> that:

Thanks, that's a more specific clue than we've had before, and I think
explains why nobody else could reproduce the bug.  You need a
rate_exceeded event to trigger it.

I'm now betting this bug was introduced by the changed handling of KOD
packets in Daniel's refactoring of the protcol engine. That tells me
where to look.

I'll put some attention on this immediately.  I think it is quite likely
that it will be trivial to fix once I have identified the exact defect.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.