| Re: [chrony-users] Root delay and Root dispersion values in `chronyc ntpdata' |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Root delay and Root dispersion values in `chronyc ntpdata'
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 23 Aug 2017 16:40:32 +0200
- Authentication-results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 35CCA404330
On Mon, Aug 14, 2017 at 11:17:58AM +0300, Horia Muntean wrote:
> On Mon, Aug 14, 2017 at 11:09 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> > I'm not sure if that is safe to assume. I think the error could go up
> > and then down in the interval. The question is what should be reported
> > in the log in order to give an estimate of maximum error.
> >
> > - root dispersion right after the update
> > - root dispersion right before the update
> > - a combination of the two
> Considering both provide valuable info why not both ?
The latest code in git produces three additional fields in the
tracking log: root delay, root dispersion and maximum error using root
delay and dispersion as it is right before the update. I wasn't able
to figure out a good way to combine the data before and after update.
It can be improved later.
--
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.