On 2008-08-28, Dave Holland <[EMAIL PROTECTED]> wrote:
> Darryl Miles <[EMAIL PROTECTED]> wrote:
>
>>I guess an offset of 0.0000 is perfect ?
>
> Yes.
Remember that these stats are just a snapshot. The real indicator of
clock stability is to summarize the stats over a long period of time.
The peer.awk utility in the scripts directory may be used for this
purpose. For example, the system at my desk shows:
$ awk -f peer.awk /var/log/ntpstats/peerstats
ident cnt mean rms max delay dist disp
==============================================================
192.168.19.4 66 -1.412 1.410 3.703 1.339 21.965 17.137
>>Now how do I tell the difference between an offset being reported as
>>0.0000 due to no sync and an offset being reported as 0.0000 due to a
>>perfect sync ?
>
> Look at the output of that command while (say) NTP is starting up and
> not yet synchronised:
>
> assID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart,
> offset=0.000
>
> compared to normal running:
>
> assID=0 status=0644 leap_none, sync_ntp, 4 events, event_peer/strat_chg,
The status bits are decoded on that line:
0xxx == leap_none
x6xx == sync_ntp
xx4x == 4 events
xxx4 == event_peer/strat_chg
--
Steve Kostecke <[EMAIL PROTECTED]>
NTP Public Services Project - http://support.ntp.org/
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.org/mailman/listinfo/questions
