| Re: 答复: 答复: [chrony-users] how to get the status of chronyd in namespace |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: 答复: 答复: [chrony-users] how to get the status of chronyd in namespace
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 24 Nov 2022 09:40:36 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1669279240; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=YrKI44u9jheF0VtGNsgL+YRdaaVvDX74iSERm5baGic=; b=a+GKnyZ3tVxUL9kEC/KrriV7DFTuN7xANQ+xS3hR91ebVJ0DG9xt+wYYvpLfzOxA2pu9pf ZiO84dRnBhdXNFt+IXDEeg/w/D9hiFp6/jLBdpXdFVSuuDzyIG2rYUju/IFE05FKANpL3J SnHyOQHSI9eEEmmX8Tf2LJ6X3fMr1u8=
On Thu, Nov 24, 2022 at 08:13:45AM +0000, chengyechun wrote:
> It takes more than 10 minutes to synchronize data from the client to the server. The client log is as follows:
It takes 10 minutes after starting a chronyd instance configured as a
client to report synchronized status when queried as a server?
And that client is configured to poll 1000 servers?
In that case, yes, that would be expected. There is a minimum interval
between client requests of 0.2 seconds (for polls >= 2s), so with 1000
servers it would be about 0.2*1000 seconds between two requests to the
same server, and up to about 600 seconds to get 3 samples and make the
first update of the clock.
If you need to specify so many servers for monitoring purposes, it
might be better to have a separate instance for that, using the
noselect option for all its sources, or the -x option to not touch the
system clock.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.