Miroslav Lichvar 1daa40a2f7 nts: use shorter NTS-KE retry interval when network is down ...

When chronyd configured with an NTS source not specified as offline and
resolvable without network was started before the network was up, it was
using an unnecessarily long NTS-KE retry interval, same as if the server
was refusing the connections.

When the network is down, the connect() call made from NKC_Start() on
the non-blocking TCP socket should fail with a different error than
EINPROGRESS and cause NKC_Start() to return with failure. Add a constant
2-second retry interval (matching default iburst) for this case.

2023-02-27 11:43:22 +01:00

19 KiB

Raw Blame History

View Raw