| 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: Tue, 8 Aug 2017 16:07:11 +0200
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com C8CE785546
On Tue, Aug 08, 2017 at 04:53:28PM +0300, Horia Muntean wrote:
> On Mon, Aug 7, 2017 at 12:11 PM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> > Yes, I think that could work. I'm wondering if it would make sense to
> > add root delay and dispersion to the tracking log.
>
> It would make sense if one wants to easily compute the estimated error
> right from an existing log.
> It can be computed from measurements.log but you must join it with
> tracking.log anyway so see what's the current source.
> More, if the source is a reference clock measurements.log will not help at all.
Ok. I agree it could be useful.
Do you think it would be better to write there the delay and
dispersion as was estimated right before the update of the clock to
get the maximum value of dispersion, or rather use the new values from
the update, assuming the user will calculate the amount of dispersion
that accumulated till the next update?
--
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.