-----邮件原件----- 发件人: Miroslav Lichvar [mailto:mlich...@redhat.com] 发送时间: 2022年11月24日 16:41 收件人: chrony-users@chrony.tuxfamily.org 主题: Re: 答复: 答复: [chrony-users] how to get the status of chronyd in namespace
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? Thank you very much for your reply, yes, but this is only a test scenario, and there is a high probability that this scenario will not be used. 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. Another question is whether the first response packet is processed after the message is sent to all servers? 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. Thank you for your advice. I'll pay attention to the actual use. -- Miroslav Lichvar -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
