| 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" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: RE: [chrony-users] Best strategy for calculating average synchronization time.
- From: "Whelan, Andy" <awhelan@xxxxxxxxxx>
- Date: Mon, 22 Jul 2024 13:56:36 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=srcinc.com; dmarc=pass action=none header.from=srcinc.com; dkim=pass header.d=srcinc.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector5401; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=bv3DLimr1IiR2OR40wjHxGLrzHcPnPazwtbkgf6zvIg=; b=PTt082LdMpqMleswqsLbNS7jfz04eVEC0ahKI+1q/1Z3o8ALYo/+h6zY59HSjO4W/+Dm32kbgl0BVY8rzW7+STBc06tIwrSwF2djJNJ2AFs7W/rZSxqh37YtKq59cox5I9yAUmoceOTe9EyFKZus5ywUqfSz0U56l1FOfEzDZEXePI/wt0GmYrmJX7Gnx8jKpRUvYrODuv4+iRdC80Z94M/HMj6tgNPONo7bKAB27+nIAikpPEwGzBC3nmbbpKfLwRpdyGv/gXvdwv/Kj+I0MQlvX4xzAuP+JHbHdeAwgbVoUlPIsFf2CE1R5L4ug7yGyR3PlU8VQZ3PzO+r1ShHFA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector5401; d=microsoft.com; cv=none; b=WFzAFPx5WrUWPjWzoxugNcHEIWtGa77/lM19HeK6uoTPGZsifwmId2tobgkqXDt1vkyATixho+HvQjkQ+Fhs1BOTjF12ROQZotryDC+ohtTMIkPnUxl1m0yIWcBRQjhFiR33Fy8IO+oblDnADJpa1gPCa2Z1nHhfZzFjFKf7LrdOB/nTZprDzx8K0isZTVQ36hbkIkOjqDCOJ/YhU7xUFWQtATFg5tUPK2jk//Roaty422LXTfcho7y/r51n6T3Q5xEAC7zErYsB5JGEK0BM06P+4J7m+KbTe8oW/x3PytT+LAdQ27M31EhlhvxgFs7bNEGXrdqDJA9TXDp7OmfrTA==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=srcinc.com;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=srcinc.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bv3DLimr1IiR2OR40wjHxGLrzHcPnPazwtbkgf6zvIg=; b=lhMz5a8NVfizlhSzI02sXI+mgIFKsNZGB0/ywVV8zhhdLgUqITSxPWuBDGxxzIqF2dzmRIKPLCfTyPpxlOglILCr1iHgSbuhNBKwMZXOKkK8BXBt1mOnOJc8UzaT60Wb3AvR0TZHed3UwD+x3JRAqoRl2BvIjXYonT5P36r3ajw=
- Thread-index: AdrYSFgMwtnic2/FTimoXgWJ5uSN/AAAfkAAAPu/Y+A=
- Thread-topic: [chrony-users] Best strategy for calculating average synchronization time.
Hi Miroslav,
Sorry I've been away (unexpectedly) for a week. Thanks very much for your response.
We are using the makestep commands as you have mentioned. It will be an embedded system that gets turned on and off a lot.
My management wants to know how fast Machine B time is converging to its time source Machine A.
Question 1: You're answer included "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"
I'm not following how I would use this second chrony instance to determine an average of how fast Machine B time is converging to its time source Machine A. Could you provide some detail?
Question 2 "Chrony -x" - So we are running 2 instances of chrony on the same machine? Does chrony -x get passed its own chrony.conf?
Thanks again for everything!
-----Original Message-----
From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Sent: Wednesday, July 17, 2024 9:08 AM
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] Best strategy for calculating average synchronization time.
Notice: This message originated outside of SRC. -- Do not click on links or open attachments unless you are sure the content is safe, and never enter your username and password.
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.
--
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.