From: Harlan Stenn Date: Thu, 9 Jan 2014 10:21:23 +0000 (-0500) Subject: [Bug 2532] Note in ntpdc docs that "enable pps" only works on older ntpd X-Git-Tag: NTP_4_2_7P411~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=70b102a8de0c9f99e38ab309b9d93e3903c931ab;p=thirdparty%2Fntp.git [Bug 2532] Note in ntpdc docs that "enable pps" only works on older ntpd bk: 52ce78235a_HTblK3uO09LE45JCSFw --- diff --git a/ChangeLog b/ChangeLog index ce6ea5039..f9f29b631 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,4 @@ +* [Bug 2532] Note in ntpdc docs that "enable pps" only works on older ntpd. (4.2.7p410) 2014/01/08 Released by Harlan Stenn * [Bug 2332] Force reference to 'libgcc_s' when using GCC, because threading+restricted user+locked memory otherwise fails on Linux. diff --git a/html/ntpdc.html b/html/ntpdc.html index 6fee231ba..0ec61a1a3 100644 --- a/html/ntpdc.html +++ b/html/ntpdc.html @@ -99,6 +99,7 @@
sysinfo
Print a variety of system state variables, i.e., state related to the local server. All except the last four lines are described in the NTP Version 3 specification, RFC-1305.
The system flags show various system flags, some of which can be set and cleared by the enable and disable configuration commands, respectively. These are the auth, bclient, monitor, pll, pps and stats flags. See the ntpd documentation for the meaning of these flags. There are two additional flags which are read only, the kernel_pll and kernel_pps. These flags indicate the synchronization status when the precision time kernel modifications are in use. The kernel_pll indicates that the local clock is being disciplined by the kernel, while the kernel_pps indicates the kernel discipline is provided by the PPS signal.
+
Note that some directives, like enable pps, are only supported on certain versions of ntpd.
The stability is the residual frequency error remaining after the system frequency correction is applied and is intended for maintenance and debugging. In most architectures, this value will initially decrease from as high as 500 ppm to a nominal value in the range .01 to 0.1 ppm. If it remains high for some time after starting the daemon, something may be wrong with the local clock, or the value of the kernel variable tick may be incorrect.
The broadcastdelay shows the default broadcast delay, as set by the broadcastdelay configuration command.
The authdelay shows the default authentication delay, as set by the authdelay configuration command.