Thanks, yes, that did the trick.
I’ve installed it on one of my test computers. It seems to work fine. I’ve
tried a couple of things that should trigger the bug, if it’s still there.
In particular, rebooting the computer then examining the journal shows that it
does get to poll all of the configured pools.
Another experiment I have tried is this:
Boot the computer and let everything settle.
un-plug the ethernet (RJ45)
restart ntpsec and watch the journal for evidence of attempts to
contact the configured pools (which will fail, since the ethernet is
disconnected)
re-plug the ethernet and continue to watch the journal for attempts to
contact the pools (which succeed this time).
In this experiment, I saw no evidence of the bug — i.e. no evidence of having
forgotten all but one of the configured pools.
Thanks for all your help!
Rick
> On Mar 25, 2019, at 4:30 PM, Richard Laager <rlaa...@wiktel.com> wrote:
>
>> sudo apt update
>> sudo apt install build-essential devscripts
>> sudo apt build-dep ntpsec
>> apt source ntpsec
>> cd ntpsec-1.1.3+dfsg1
>> patch -p1 < ~/ntpsec_1.1.3+dfsg1-3~1.gbpdde9c0.debdiff
>
> I missed a step here, as `apt source` applies the existing patches, so
> we apparently need to apply this patch too:
>
> patch -p1 < debian/patches/0001-Fix-for-577-DNS-retry-sloth.patch
>
>> debuild -uc -us
> If you can try this and confirm this patch as packaged fixes your
> problem, that would help me move forward with this.
>
> --
> Richard
