| 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: Mon, 7 Aug 2017 11:11:39 +0200
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 74A4113A4E
On Fri, Aug 04, 2017 at 11:12:08AM -0400, Chris Perl wrote:
> What I had been considering as a workaround was something like:
>
> Record the root dispersion on the server on some regular interval (say
> every few seconds or so).
>
> When looking at a given client's stats (`chronyc tracking' output)
> over some time interval, if you take the max dispersion reported by
> the server over that same interval, round up to the nearest 15us
> boundary and subtract the root dispersion, that value can be
> subtracted from the clients reported root dispersion.
Yes, I think that could work. I'm wondering if it would make sense to
add root delay and dispersion to the tracking log.
--
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.