Re: [chrony-dev] chronyc: CSV output rounds frequency fields to 3 decimals

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-dev Archives ]



October 5, 2026 at 17:14, "Miroslav Lichvar" <mlichvar@xxxxxxxxxx> wrote:
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



Hi! 

  stock chronyc 4.9              git chronyc 4.9-1-g7fab541 -E
  Last offset   : -0.000000001  Last offset   : -8.7639423e-10 seconds
  RMS offset    :  0.000000001  RMS offset    :  9.6118480e-10 seconds
  Frequency     :  0.000 ppm    Frequency     :  3.5061228e-05 ppm fast
  Residual freq : -0.000 ppm    Residual freq : -2.3620818e-07 ppm
  Skew          :  0.000 ppm    Skew          :  1.7248884e-05 ppm

can confirm this is very much more informative, greatly appreciated!)

Br
Markus Kovero




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/