NTP_ADJTIME(2) | System Calls Manual | NTP_ADJTIME(2) |
ntp_adjtime
,
ntp_gettime
— Network Time
Protocol (NTP) daemon interface system calls
Standard C Library (libc, -lc)
#include
<sys/timex.h>
int
ntp_adjtime
(struct
timex *);
int
ntp_gettime
(struct
ntptimeval *);
The two system calls
ntp_adjtime
()
and ntp_gettime
() are the kernel interface to the
Network Time Protocol (NTP) daemon ntpd(8).
The
ntp_adjtime
()
function is used by the NTP daemon to adjust the system clock to an
externally derived time. The time offset and related variables which are set
by ntp_adjtime
() are used by
hardclock
()
to adjust the phase and frequency of the phase- or frequency-lock loop (PLL
resp. FLL) which controls the system clock.
The
ntp_gettime
()
function provides the time, maximum error (sync distance) and estimated
error (dispersion) to client user application programs.
In the following, all variables that refer PPS are only relevant if the PPS_SYNC option is enabled in the kernel.
ntp_adjtime
()
has as argument a struct timex * of the following
form:
struct timex { unsigned int modes; /* clock mode bits (wo) */ long offset; /* time offset (us) (rw) */ long freq; /* frequency offset (scaled ppm) (rw) */ long maxerror; /* maximum error (us) (rw) */ long esterror; /* estimated error (us) (rw) */ int status; /* clock status bits (rw) */ long constant; /* pll time constant (rw) */ long precision; /* clock precision (us) (ro) */ long tolerance; /* clock frequency tolerance (scaled * ppm) (ro) */ /* * The following read-only structure members are implemented * only if the PPS signal discipline is configured in the * kernel. */ long ppsfreq; /* pps frequency (scaled ppm) (ro) */ long jitter; /* pps jitter (us) (ro) */ int shift; /* interval duration (s) (shift) (ro) */ long stabil; /* pps stability (scaled ppm) (ro) */ long jitcnt; /* jitter limit exceeded (ro) */ long calcnt; /* calibration intervals (ro) */ long errcnt; /* calibration errors (ro) */ long stbcnt; /* stability limit exceeded (ro) */ };
The members of this struct have the following
meanings when used as argument for
ntp_adjtime
():
ntp_adjtime
() call (write-only). Bitwise OR of the
following:
ntp_adjtime
() call, and increased by the kernel
once each second to reflect the maximum error bound growth
(read-write).ntp_adjtime
(), but unused by the kernel
(read-write).ntp_adjtime
() call, the struct
timex * structure contains the current values of the corresponding
variables.
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:
ntp_adjtime
() and
ntp_gettime
() return the current state of the clock
on success, or any of the errors of copyin(9) and
copyout(9). ntp_adjtime
() may
additionally return EPERM
if the user calling
ntp_adjtime
() does not have sufficient
permissions.
Possible states of the clock are:
The ntp_adjtime
() system call may return
EPERM
if the caller does not have sufficient
permissions.
options(4), ntpd(8), hardclock(9), hz(9)
Take note that this API is extremely complex and stateful. Users should not attempt modification without first reviewing the ntpd(8) sources in depth.
July 13, 2005 | Debian |