Re: [Linuxptp-users] phc2sys produces excessive log messages

[Richard C. <ric...@gm...>]

On Thu, Apr 18, 2019 at 02:44:10PM -0400, Charles Curley wrote:
> While I like to see some messages from time to time from phc2sys it is
> really filling my systemd journal up w/ a message every second. I have
> changed the log level to 5 but now it doesn't seem to ever report what the
> offset is. Could there be an option to report if it exceeds a threshold or
> something like "summary_interval" that ptp4l has?

Use the '-u' command line option:

       -u summary-updates
              Specify the number of clock updates included in summary  statis‐
              tics. The statistics include offset root mean square (RMS), max‐
              imum absolute offset, frequency offset mean and standard  devia‐
              tion, and mean of the delay in clock readings and standard devi‐
              ation. The units are nanoseconds and parts per billion (ppb). If
              zero,  the individual samples are printed instead of the statis‐
              tics. The messages are  printed  at  the  LOG_INFO  level.   The
              default is 0 (disabled).

Example with -u 10

phc2sys[277.514]: eth6 rms  109 max  218 freq -33282 +/-  68 delay  5536 +/-  17
phc2sys[287.515]: eth6 rms   48 max   80 freq -33192 +/-  37 delay  5532 +/-  22
phc2sys[297.517]: eth6 rms   35 max   69 freq -33118 +/-  32 delay  5537 +/-  19
phc2sys[307.518]: eth6 rms   47 max   84 freq -33020 +/-  30 delay  5544 +/-  18
phc2sys[317.520]: eth6 rms   34 max   55 freq -32962 +/-  29 delay  5527 +/-  24
phc2sys[327.521]: eth6 rms   41 max   87 freq -32886 +/-  34 delay  5534 +/-  16
phc2sys[337.523]: eth6 rms   44 max  100 freq -32814 +/-  37 delay  5536 +/-  19

HTH,
Richard