| Re: [chrony-dev] chronyc: CSV output rounds frequency fields to 3 decimals |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: Markus Kovero <mui@xxxxxx>
- Subject: Re: [chrony-dev] chronyc: CSV output rounds frequency fields to 3 decimals
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 5 Oct 2026 16:14:45 +0200
- Cc: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1791209695; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ULkmq2dm9yxH87poBMeSc02x78IVMkBWtwKvas2HJ3E=; b=b7oLo/RdaY6QQXvLKyM7Eq1EuQwl0I5xL7gSnXiCdcj4vFiAJXhpTk+Iy52jGIhWc1HtVB m1uT/ClQSNimFHcCa2pbZXYxgnvVVdVD4p74TuqcQyIwnKZ0mqjcURUfkLLgVZgWDrmSJB zR70dRi0np7BkqVABtOF7nZ7K78VvMQ=
On Tue, Sep 22, 2026 at 09:21:37AM +0000, Markus Kovero wrote:
> That sounds better than what I suggested — matching the digits to the
> wire format handles the large-value case my fixed-precision idea would
> have got wrong, and it covers skew reading 0 as well. Happy to test a
> patch on a rubidium-referenced host if that is useful; the offset here
> sits around 2e-11, so it exercises the small end.
The latest code in git now has -E option to use the %e notation.
It should work in both normal and CSV modes. In the normal mode the
precision is adjusted to not break the alignment of the reports, so
some values like skew in sources report have only one significant
digit, but in the tracking report it has full precision.
--
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.