| Re: [chrony-users] Chrony not taking SOCKET data from Application |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chrony not taking SOCKET data from Application
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 7 Feb 2023 09:34:47 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675758890; 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=0YaReKscE/JaPV0Mvu46V6OfVEvpwIkjaPt91gkbKxk=; b=LoPrLlVw/084gByYlaVu3rlSUckxie7hvHBvkjbIHem0ktiw7uo8R7qXTXZ90OCtI6xlaJ I11/5bK3Casb1Y1ktMf1ygzShu49gjyWoW8zglvqX3vprz7GQfpoxYRBPF7DxalBSr+3ht UwnWDWR4CMxh2fI/WNCzqMUMTf2L4lU=
On Tue, Feb 07, 2023 at 12:04:53PM +0530, sarveshwar k wrote:
> > The reason for chronyc sources sometimes showing 2 as LastRx, even
> > when no samples are lost, seems to be incorrect rounding of the sample
> > time. I can fix that.
>
> Will there be a release for this fix.
> Current version I am using is 3.5 of chrony for which yocto recipe exists.
It will be in the next release. Backport the commit dec07aa844f8 from
the chrony repository to 3.5 shouldn't be too difficult. It's not
actually a bug, but rather a data-minimization feature which is not
necessary for reference clocks.
--
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.