> Assuming this isn't blocking the daemon generally, I'd probably leave it to
> the default. I can't immediately come up with a justification as to why
> NTS-KE is different from other TCP protocols. I'm not very confident in this
> answer, though, so take this with a grain of salt.
There
On 4/4/19 5:36 AM, Hal Murray via devel wrote:
> How long should NTS-KE wait?
>
> The current code uses 3 seconds, but I missed the connect() so it uses the
> default for that which is ballpark of 2 minutes.
Assuming this isn't blocking the daemon generally, I'd probably leave it
to the
How long should NTS-KE wait?
The current code uses 3 seconds, but I missed the connect() so it uses the
default for that which is ballpark of 2 minutes.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
