client: don't shorten default timeout with ASYNCDNS
With connected sockets recv() should fail immediately if chronyd is not listening on localhost and with the Unix socket connecting should fail.
This commit is contained in:
parent
38ac2b39ce
commit
cec7c44f61
2 changed files with 1 additions and 6 deletions
|
@ -4526,9 +4526,7 @@ in milliseconds. If no response is received from @code{chronyd}, the timeout is
|
|||
doubled and the request is resent. The maximum number of retries is configured
|
||||
with the @code{retries} command (@pxref{retries command}).
|
||||
|
||||
By default, the timeout is 1000 milliseconds or 100 milliseconds if
|
||||
@code{chronyc} is contacting localhost (i.e. the `-h' option wasn't specified)
|
||||
and @code{chronyd} was compiled with asynchronous name resolving.
|
||||
By default, the timeout is 1000 milliseconds.
|
||||
@c }}}
|
||||
@c {{{ tracking
|
||||
@node tracking command
|
||||
|
|
3
client.c
3
client.c
|
@ -2710,9 +2710,6 @@ main(int argc, char **argv)
|
|||
|
||||
if (!hostnames) {
|
||||
hostnames = DEFAULT_COMMAND_SOCKET",127.0.0.1,::1";
|
||||
#ifdef FEAT_ASYNCDNS
|
||||
initial_timeout /= 10;
|
||||
#endif
|
||||
}
|
||||
|
||||
UTI_SetQuitSignalsHandler(signal_handler);
|
||||
|
|
Loading…
Reference in a new issue