Interpreting NTP status
Steve Burton
steve at sliderule.demon.co.uk
Sun Jul 9 15:41:19 UTC 2017
On 09/07/2017 15:39, Carmel NY wrote:
> A while back, I was receiving an error message about an outdated “leap
> second” file. I Googled around and found an article that said to put
> the following in the “rc.conf” file to correct the problem:
>
> # NTPD
> ntpd_enable="YES"
> ntpd_sync_on_start="YES"
> ntp_leapfile_fetch_verbose="YES"
> ntp_leapfile_sources=ftp://tycho.usno.navy.mil/pub/ntp/leap-seconds.list
>
> Then, I found another article that said to put this in the
> “/etc/periodic.conf” file get information on the NTPD program:
>
> # 480.leapfile-ntpd
> daily_ntpd_leapfile_enable="YES" # Fetch NTP leapfile
> daily_ntpd_avoid_congestion="YES" # Avoid congesting leapfile sources
>
> # 480.status-ntpd
> daily_status_ntpd_enable="YES" # Check NTP status
>
> Now, in the “daily run output” email, I find this:
>
> NTP status:
> remote refid st t when poll reach delay offset jitter
> ==============================================================================
> +198.55.111.50 133.157.29.35 3 u 760 1024 377 87.913 5.793 18.418
> *192.155.90.13 142.66.101.13 2 u 264 1024 377 45.449 -2.235 2.925
> 2607:fa18::2407 .STEP. 16 u - 1024 0 0.000 0.000 0.000
>
> I am hoping someone can tell me exactly what this means. I cannot find
> any documentation on how to interpret this.
>
Check man ntpq(8)
Steve.
More information about the freebsd-questions
mailing list