| RE: [chrony-dev] timex kernel offset parameter not updated |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: "chrony-dev@xxxxxxxxxxxxxxxxxxxx" <chrony-dev@xxxxxxxxxxxxxxxxxxxx>
- Subject: RE: [chrony-dev] timex kernel offset parameter not updated
- From: Filip Verwee <fverwee@xxxxxxxxxxxxx>
- Date: Tue, 12 Mar 2024 08:35:43 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=synamedia.com; dmarc=pass action=none header.from=synamedia.com; dkim=pass header.d=synamedia.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; 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=DzWiONeD10A5RMVrZN98oAOeohaMEnaipGCyX66VRrA=; b=eykannqp1Xl9yPYGpcDPGdRhNAb7saJYNorqQWC//WkgNRmDF6QyrK4/HhaOP8TgqRZbJsTXyhI6msZk8WsbgeHWw0c6Lu9ZGXgJoNswrYVLRSTShnvuOwyYt0XHsn4GOZl6bLPpIVAOHT8thUGoisFA1YhnGIHmqb4XXrUAI3buQlIQLg7CIrAJLlT/6DqXrWIFiPg9Wbp3eBpDmXSF+i9R0FbcIHW4RdOgQjrSm5BVVgTGUGk1LLI4UNQn7gWp7X1FNSRnOisB8DaSJ/KbWOy/0k8NFME870BZ27JUfFrG5WsmJ/53eBvp0kLJV8+dqEZsKMX4+/l/OwewinCqLw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=m439gaSRTdWRp1qqU8bZse+ahcZCJCGNQBR3se6UwAS9tvuiEJqE0Fl3xuffMwRqeRuUQ8DFMHoi+cL86vwPhQ2lgHVoXuf142x2xSs37h20Mg/Vldw+1gcF2IL9OIDSVZ9eJJX7qQLl4s9ZBSbLfaje7tZPUdZ+nUX+VA6UFxtX+KJpJoZgPrH9tYO60FjBwbvt1I34Bc80qNhopQnmHPbD25TUCAIPGACtDAIqGDx6wrJPjxi7BOXbB7+QlApbTJDa9Y1/jf56MNzjkelyxmhQSEUdA3DgdNiDaa6DRI5NBNL9umkt1y2Jr73JCUzxdCI0Ez6gopfmdP5ZqzJaOQ==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=synamedia.com;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=synamedia.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DzWiONeD10A5RMVrZN98oAOeohaMEnaipGCyX66VRrA=; b=U4/xfvZ+vhda4GNKD715Zl7bEEX/BbtF93EgsYXSo/dz9pShXWXxnFn/OGXsHQKTkTgzSi1r1R9Jku8VRIlAdj1qLR9qZ+ahoY2N9GkjzcnYm1gBB6sBVRpQdH3E5xg3j1vwYt2dIAzyYRghKuyvnfepWyLDJAnKlZAPzjXfxhcSch29S3Q1YGUeoJKqCtdxI5NfZuvmpalTZ2PLjW51GG3V/u2LRI+NHdWG9FQoESrFohOL7KPazdmIWMUktjXaZUB+gHGciL2HsLt3WTfyAUf+JkPArfJ2GOR/f+YGO3+xTCzRRdP7icPGUEvPfQg7+SFOlSVKlce7tEBzR+wmxA==
- Msip_labels: MSIP_Label_e305dca8-daac-40b2-85cb-c39a1eaa36df_ActionId=69c54e00-c08f-4fda-94ab-fef19c0eb49a;MSIP_Label_e305dca8-daac-40b2-85cb-c39a1eaa36df_ContentBits=0;MSIP_Label_e305dca8-daac-40b2-85cb-c39a1eaa36df_Enabled=true;MSIP_Label_e305dca8-daac-40b2-85cb-c39a1eaa36df_Method=Standard;MSIP_Label_e305dca8-daac-40b2-85cb-c39a1eaa36df_Name=e305dca8-daac-40b2-85cb-c39a1eaa36df;MSIP_Label_e305dca8-daac-40b2-85cb-c39a1eaa36df_SetDate=2024-03-12T08:24:55Z;MSIP_Label_e305dca8-daac-40b2-85cb-c39a1eaa36df_SiteId=ecdd899a-33be-4c33-91e4-1f1144fc2f56;
- Thread-index: Adp0UzHsEHz3W+8YSkuGEHEre7pbYAAAmJiAAABLwPA=
- Thread-topic: [chrony-dev] timex kernel offset parameter not updated
Hi Miroslav,
Thanks for the reply.
Even if chronyd is not using the kernel PLL, wouldn't it be still possible to update the offset parameter?
Regards,
Filip Verwee.
-----Original Message-----
From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Sent: Tuesday, March 12, 2024 9:16 AM
To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-dev] timex kernel offset parameter not updated
On Tue, Mar 12, 2024 at 08:04:04AM +0000, Filip Verwee wrote:
> Dear,
>
> On our cluster nodes we use node-exporter to collect the timex information from the kernel. The advantage of using the node-exporter timex collector is that it is independent of the NTP implementation used on the nodes (ntpd, chrony...). Unfortunately, it looks like chrony is not updating the timex kernel offset parameter. Its value is always '0' while on nodes using ntpd, the timex kernel offset parameter represents the time offset in between local system and reference clock.
> This seems like a shortcoming in chrony. Are there any plans to implement this functionality in the near future?
That is not possible as chronyd doesn't use the kernel PLL. The closest thing to the kernel PLL offset would be the chronyc tracking offset.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.