"Poul-Henning Kamp" writes:
> --------
> In message <546152ac.8090...@rubidium.dyndns.org>, Magnus Danielson writes:
>
> >Monitoring as such is an important task, and some of the NTP clients
> >might be servers in other contexts, and then it makes sense to monitor
> >that they got their NTP time into shape.
>
> For which there has existed a system call for 20 years now:
>
> ntp_gettime() has as argument a struct ntptimeval * with the following
> members:
>
> struct ntptimeval {
> struct timeval time; /* current time (ro) */
> long maxerror; /* maximum error (us) (ro) */
> long esterror; /* estimated error (us) (ro) */
> };
>
> These have the following meaning:
> time Current time (read-only).
> maxerror Maximum error in microseconds (read-only).
> esterror Estimated error in microseconds (read-only).
And those fields have value, and they are not "enough". The aim of
NTF's General Timestamp API is to have a timestamp with "enough" values
in it.
--
Harlan Stenn <st...@ntp.org>
http://networktimefoundation.org - be a member!
_______________________________________________
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
