[time-nuts] future NTP programs...
Poul-Henning Kamp
phk at phk.freebsd.dk
Tue Nov 11 00:15:20 UTC 2014
--------
In message <546152AC.8090307 at 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).
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
More information about the Time-nuts_lists.febo.com
mailing list