[Bug 2532] Note in ntpdc docs that "enable pps" only works on older ntpd

bk: 52ce78235a_HTblK3uO09LE45JCSFw

diff --git a/ChangeLog b/ChangeLog
index ce6ea50396959da1e76b3e4e26cbcf6919a21c5c..f9f29b631e83913922206d04c77b8f9698991cfd 100644 (file)
--- 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 <stenn@ntp.org>
 * [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 6fee231bac3919ea802d8f8ddc926c325398108b..0ec61a1a38e5ad5c4d59562ac8d356233f3cbfe8 100644 (file)
--- a/html/ntpdc.html
+++ b/html/ntpdc.html
@@ -99,6 +99,7 @@
   <dt><tt>sysinfo</tt></dt>
   <dd>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.</dd>
   <dd>The <tt>system flags</tt> show various system flags, some of which can be set and cleared by the <tt>enable</tt> and <tt>disable</tt> configuration commands, respectively. These are the <tt>auth</tt>, <tt>bclient</tt>, <tt>monitor</tt>, <tt>pll</tt>, <tt>pps</tt> and <tt>stats</tt> flags. See the <tt>ntpd</tt> documentation for the meaning of these flags. There are two additional flags which are read only, the <tt>kernel_pll</tt> and <tt>kernel_pps</tt>. These flags indicate the synchronization status when the precision time kernel modifications are in use. The <tt>kernel_pll</tt> 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.</dd>
+  <dd>Note that some directives, like <tt>enable pps</tt>, are only supported on certain versions of <tt>ntpd</tt>.</dd>
   <dd>The <tt>stability</tt> 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 <tt>tick</tt> may be incorrect.</dd>
   <dd>The <tt>broadcastdelay</tt> shows the default broadcast delay, as set by the <tt>broadcastdelay</tt> configuration command.</dd>
   <dd>The <tt>authdelay</tt> shows the default authentication delay, as set by the <tt>authdelay</tt> configuration command.</dd>