From 3e3f045ab70ebcefe818693fb8fabf3baa634774 Mon Sep 17 00:00:00 2001 From: Miroslav Lichvar Date: Mon, 5 Aug 2019 18:15:38 +0200 Subject: [PATCH] doc: improve ntpdate answer in FAQ --- doc/faq.adoc | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/faq.adoc b/doc/faq.adoc index 04cdae8..9c628b7 100644 --- a/doc/faq.adoc +++ b/doc/faq.adoc @@ -244,6 +244,18 @@ specified on the command line. For example: # chronyd -q 'pool pool.ntp.org iburst' ---- +The command above would normally take about 5 seconds if the servers were +well synchronised and responding to all requests. If not synchronised or +responding, it would take about 10 seconds for `chronyd` to give up and exit +with a non-zero status. A faster configuration is possible. A single server can +be used instead of four servers, the number of measurements can be reduced with +the `maxsamples` option, and a timeout can be specified with the `-t` option. +The following command would take only up to about 1 second. + +---- +# chronyd -q -t 1 'server pool.ntp.org iburst maxsamples 1' +---- + === Can `chronyd` be configured to control the clock like `ntpd`? It is not possible to perfectly emulate `ntpd`, but there are some options that