| Re: [chrony-dev] timex kernel offset parameter not updated |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] timex kernel offset parameter not updated
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 12 Mar 2024 09:16:27 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1710231389; 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=tPcqcC6r/7G6/CZakTSO7mfdY0aFNzcXM88yDCkyYJE=; b=W9UM9qeAwKTLpjIJP+ypeu8ugzV5gtkVf/sbJ872ccnhRvPJjXxqM11bxP+gTkyZMRb64q hiDpRmYbkjCQzXFLyih3pAUP7hSuzcZOw75iLWE1Jvp5z5LyeHYrnpInmC56I3OKEP5vo5 iwYdVhinuYA2/PY0zbgNjO6mTyJEaNk=
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.