On 12/1/19 2:44 AM, Achim Gratz via devel wrote: > Richard Laager via devel writes: >> The issue persists when removing "nts" from "server" lines (i.e. >> disabling NTS client behavior). >> >> The problem goes away when disabling NTS server behavior.
To clarify: If I run as an NTS client but not NTS server, then I get the "blocked for" errors on startup, but not past that (in short tests). > I don't serve NTS from the two test machines, so that would be an > additional code path to consider. So the NTS serving is probably why I get them on an ongoing basis and you don't. We both get them on startup from the DNS code. -- Richard
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
