diff -up ntp-4.2.6p5/html/authopt.html.htmldoc ntp-4.2.6p5/html/authopt.html
--- ntp-4.2.6p5/html/authopt.html.htmldoc 2011-07-11 04:18:25.000000000 +0200
+++ ntp-4.2.6p5/html/authopt.html 2013-03-28 18:04:38.581260191 +0100
@@ -364,7 +364,7 @@ UTC</p>
are left unspecified, the default names are used as described below. Unless
the complete path and name of the file are specified, the location of a file
is relative to the keys directory specified in the <tt>keysdir</tt> configuration
- command or default <tt>/usr/local/etc</tt>. Following are the options.</dd>
+ command or default <tt>/etc/ntp/crypto</tt>. Following are the options.</dd>
<dd><dl>
@@ -396,7 +396,7 @@ UTC</p>
<dd>Specifies the complete path to the MD5 key file containing the keys and key IDs used by <tt>ntpd</tt>, <tt>ntpq</tt> and <tt>ntpdc</tt> when operating with symmetric key cryptography. This is the same operation as the <tt>-k </tt>command line option. Note that the directory path for Autokey media is specified by the <tt>keysdir</tt> command.</dd>
<dt id="keysdir"><tt>keysdir <i>path</i></tt>K</dt>
-<dd>This command specifies the default directory path for Autokey cryptographic keys, parameters and certificates. The default is <tt>/usr/local/etc/</tt>. Note that the path for the symmetric keys file is specified by the <tt>keys</tt> command.</dd>
+<dd>This command specifies the default directory path for Autokey cryptographic keys, parameters and certificates. The default is <tt>/etc/ntp/crypto</tt>. Note that the path for the symmetric keys file is specified by the <tt>keys</tt> command.</dd>
<dt id="requestkey"><tt>requestkey <i>keyid</i></tt></dt>
<dd>Specifies the key ID to use with the
diff -up ntp-4.2.6p5/html/keygen.html.htmldoc ntp-4.2.6p5/html/keygen.html
--- ntp-4.2.6p5/html/keygen.html.htmldoc 2011-07-11 04:18:26.000000000 +0200
+++ ntp-4.2.6p5/html/keygen.html 2013-03-28 18:04:38.581260191 +0100
@@ -206,7 +206,6 @@
<p>All cryptographically sound key generation schemes must have means to randomize the entropy seed used to initialize the internal pseudo-random number generator used by the OpenSSL library routines. If a site supports <tt>ssh</tt>, it is very likely that means to do this are already available. The entropy seed used by the OpenSSL library is contained in a file, usually called <tt>.rnd</tt>, which must be available when starting the <tt>ntp-keygen</tt> program or <tt>ntpd</tt> daemon.</p>
<p>The OpenSSL library looks for the file using the path specified by the <tt>RANDFILE</tt> environment variable in the user home directory, whether root or some other user. If the <tt>RANDFILE</tt> environment variable is not present, the library looks for the <tt>.rnd</tt> file in the user home directory. Since both the <tt>ntp-keygen</tt> program and <tt>ntpd</tt> daemon must run as root, the logical place to put this file is in <tt>/.rnd</tt> or <tt>/root/.rnd</tt>. If the file is not available or cannot be written, the program exits with a message to the system log.</p>
-<p>On systems that provide /dev/urandom, the randomness device is used instead and the file specified by the <tt>randfile</tt> subcommand or the <tt>RANDFILE</tt> environment variable is ignored.</p>
<h4 id="priv">Cryptographic Data Files</h4>
diff -up ntp-4.2.6p5/html/ntpd.html.htmldoc ntp-4.2.6p5/html/ntpd.html
--- ntp-4.2.6p5/html/ntpd.html.htmldoc 2011-07-11 04:18:26.000000000 +0200
+++ ntp-4.2.6p5/html/ntpd.html 2013-03-28 18:05:21.174228349 +0100
@@ -143,26 +143,8 @@
<dd>Specify a user, and optionally a group, to switch to. This option is only available if the OS supports running the server without full root privileges. Currently, this option is supported under NetBSD (configure with <tt>--enable-clockctl</tt>) and Linux (configure with --<tt>enable-linuxcaps</tt>).</dd>
<dt><tt>-U <i>interface update interval</i></tt></dt>
<dd>Number of seconds to wait between interface list scans to pick up new and delete network interface. Set to 0 to disable dynamic interface list updating. The default is to scan every 5 minutes.</dd>
- <dt><tt>-v <i>variable</i></tt></dt>
- <dt><tt>-V <i>variable</i></tt></dt>
- <dd>Add a system variable listed by default.</dd>
<dt><tt>-x</tt></dt>
<dd>Normally, the time is slewed if the offset is less than the step threshold, which is 128 ms by default, and stepped if above the threshold. This option sets the threshold to 600 s, which is well within the accuracy window to set the clock manually. Note: Since the slew rate of typical Unix kernels is limited to 0.5 ms/s, each second of adjustment requires an amortization interval of 2000 s. Thus, an adjustment as much as 600 s will take almost 14 days to complete. This option can be used with the <tt>-g</tt> and <tt>-q</tt> options. See the <tt>tinker</tt> command for other options. Note: The kernel time discipline is disabled with this option.</dd>
- <dt><tt>--pccfreq <i>frequency</i></tt></dt>
- <dd>Substitute processor cycle counter for QueryPerformanceCounter unconditionally
- using the given frequency (in Hz). <tt>--pccfreq</tt> can be used on systems
- which do not use the PCC to implement QueryPerformanceCounter
- and have a fixed PCC frequency. The frequency specified must
- be accurate within 0.5 percent. <tt>--usepcc</tt> is equivalent on many systems and should
- be tried first, as it does not require determining the frequency
- of the processor cycle counter. For x86-compatible processors, the PCC is
- also referred to as <tt>RDTSC</tt>, which is the assembly-language instruction to retrieve
- the current value. (Windows only)</dd>
- <dt><tt>--usepcc</tt></dt>
- <dd>Substitute processor cycle counter for QueryPerformanceCounter if they
- appear equivalent. This option should be used only if the PCC
- frequency is fixed. Power-saving functionality on many laptops varies the
- PCC frequency. (Windows only)</dd>
</dl>
<h4 id="cfg">The Configuration File</h4>
<p>Ordinarily, <tt>ntpd</tt> reads the <tt>ntp.conf</tt> configuration file at startup in order to determine the synchronization sources and operating modes. It is also possible to specify a working, although limited, configuration entirely on the command line, obviating the need for a configuration file. This may be particularly useful when the local host is to be configured as a broadcast client, with servers determined by listening to broadcasts at run time.</p>
@@ -214,14 +196,14 @@
</tr>
<tr>
<td width="30%">statistics path</td>
- <td width="30%"><tt>/var/NTP</tt></td>
+ <td width="30%"><tt>/var/log/ntpstats/</tt></td>
<td width="20%"><tt>-s</tt></td>
<td width="20%"><tt>statsdir</tt></td>
</tr>
<tr>
<td width="30%">keys path</td>
- <td width="30%"><tt>/usr/local/etc</tt></td>
- <td width="20%"><tt>-k</tt></td>
+ <td width="30%"><tt>/etc/ntp/crypto</tt></td>
+ <td width="20%"><tt>none</tt></td>
<td width="20%"><tt>keysdir</tt></td>
</tr>
</table>
diff -up ntp-4.2.6p5/html/ntpdate.html.htmldoc ntp-4.2.6p5/html/ntpdate.html
--- ntp-4.2.6p5/html/ntpdate.html.htmldoc 2013-03-28 18:04:38.556260210 +0100
+++ ntp-4.2.6p5/html/ntpdate.html 2013-03-28 18:04:38.582260190 +0100
@@ -43,7 +43,7 @@
<dt><tt>-e <i>authdelay</i></tt>
<dd>Specify the processing delay to perform an authentication function as the value <i>authdelay</i>, in seconds and fraction (see <tt>ntpd</tt> for details). This number is usually small enough to be negligible for most purposes, though specifying a value may improve timekeeping on very slow CPU's.
<dt><tt>-k <i>keyfile</i></tt>
- <dd>Specify the path for the authentication key file as the string <i>keyfile</i>. The default is <tt>/etc/ntp.keys</tt>. This file should be in the format described in <tt>ntpd</tt>.
+ <dd>Specify the path for the authentication key file as the string <i>keyfile</i>. The default is <tt>/etc/ntp/keys</tt>. This file should be in the format described in <tt>ntpd</tt>.
<dt><tt>-o <i>version</i></tt>
<dd>Specify the NTP version for outgoing packets as the integer <i>version</i>, which can be 1 or 2. The default is 4. This allows <tt>ntpdate</tt> to be used with older NTP versions.
<dt><tt>-p <i>samples</i></tt>
@@ -66,7 +66,7 @@
<h4>Diagnostics</h4>
<tt>ntpdate</tt>'s exit status is zero if it finds a server and updates the clock, and nonzero otherwise.
<h4>Files</h4>
- <tt>/etc/ntp.keys</tt> - encryption keys used by <tt>ntpdate</tt>.
+ <tt>/etc/ntp/keys</tt> - encryption keys used by <tt>ntpdate</tt>.
<h4>Bugs</h4>
The slew adjustment is actually 50% larger than the measured offset, since this (it is argued) will tend to keep a badly drifting clock more accurate. This is probably not a good idea and may cause a troubling hunt for some values of the kernel variables <tt>tick</tt> and <tt>tickadj</tt>.
<hr>
diff -up ntp-4.2.6p5/html/ntptime.html.htmldoc ntp-4.2.6p5/html/ntptime.html
--- ntp-4.2.6p5/html/ntptime.html.htmldoc 2009-12-09 08:36:36.000000000 +0100
+++ ntp-4.2.6p5/html/ntptime.html 2013-03-28 18:13:56.921842773 +0100
@@ -17,7 +17,7 @@
<br clear="left">
<hr>
<h4>Synopsis</h4>
- <tt>ntptime [ -chr ] [ -e <i>est_error</i> ] [ -f <i>frequency</i> ] [ -m <i>max_error</i> ] [ -o <i>offset</i> ] [ -s <i>status</i> ] [ -t <i>time_constant</i>]</tt>
+ <tt>ntptime [ -MNchr ] [ -e <i>est_error</i> ] [ -f <i>frequency</i> ] [ -m <i>max_error</i> ] [ -o <i>offset</i> ] [ -s <i>status</i> ] [ -t <i>time_constant</i>] [ -T <i>tai_offset</i> ]</tt>
<h4>Description</h4>
<p>This program is useful only with special kernels described in the <a href="kern.html">A Kernel Model for Precision Timekeeping</a> page. It reads and displays time-related kernel variables using the <tt>ntp_gettime()</tt> system call. A similar display can be obtained using the <tt>ntpdc</tt> program and <tt>kerninfo</tt> command.</p>
<h4>Options</h4>
@@ -40,9 +40,15 @@
<dd>Specify clock status. Better know what you are doing.
<dt><tt>-t <i>time_constant</i></tt>
<dd>Specify time constant, an integer in the range 0-10.
+ <dt><tt>-M</tt>
+ <dd>Switch to microsecond mode.
+ <dt><tt>-N</tt>
+ <dd>Switch to nanosecond mode.
+ <dt><tt>-T <i>tai_offset</i></tt>
+ <dd>Set TAI offset.
</dl>
<hr>
<script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
</body>
-</html>
\ No newline at end of file
+</html>