| Re: [chrony-users] Best strategy for calculating average synchronization time. |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Best strategy for calculating average synchronization time.
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 17 Jul 2024 15:07:46 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1721221673; 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=dA/yuniyB28CABRgm1NEIhDYZrxvV90sNcPC7pP7GbY=; b=G/hzC23FveGBLFeAQ6tu+YfBMyrX0Us75xYhwszYc6jM8vTjRESckynUAwT4nTaFEB3KqL iKO6carFdQJFBU2dDwjkvAiyRzwEFUVrgbcQPbR1F75LILp7peA7xLjuVH9SrViS/SQKQC JzF4PQqLabDXzg40zRnSPOhZ6HyZlRI=
On Wed, Jul 17, 2024 at 12:53:47PM +0000, Whelan, Andy wrote:
> I want to try to try a bunch of experiments where we manually change the times on machine B and monitor how fast the system time on machine B synchronizes to, say within a second of Machine A. I want to calculate an average synchronization time.
You would need an independent process measuring the error of the
system clock. It could be a second chronyd instance running with the
-x option using a much shorter polling interval.
Please note that if you step the system clock of machine B behind
chrony's back, you will disrupt its loop and it might take longer to
recover than if you stepped the server's clock, or stepped the B's
clock by using the chronyc settime and makestep commands.
--
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.