diff options
Diffstat (limited to 'html')
| -rw-r--r-- | html/.datecheck | 0 | ||||
| -rw-r--r-- | html/clockopt.html | 9 | ||||
| -rw-r--r-- | html/copyright.html | 4 | ||||
| -rw-r--r-- | html/release.html | 2 |
4 files changed, 9 insertions, 6 deletions
diff --git a/html/.datecheck b/html/.datecheck new file mode 100644 index 000000000000..e69de29bb2d1 --- /dev/null +++ b/html/.datecheck diff --git a/html/clockopt.html b/html/clockopt.html index 5b2de7e58d6e..5a721a8a745e 100644 --- a/html/clockopt.html +++ b/html/clockopt.html @@ -29,8 +29,8 @@ <dd>Marks the reference clock as preferred. All other things being equal, this host will be chosen for synchronization among a set of correctly operating hosts. See the <a href="prefer.html">Mitigation Rules and the <tt>prefer</tt> Keyword</a> page for further information.</dd> <dt><tt>mode <i>int</i></tt></dt> <dd>Specifies a mode number which is interpreted in a device-specific fashion. For instance, it selects a dialing protocol in the ACTS driver and a device subtype in the <tt>parse</tt> drivers.</dd> - <dt><tt>minpoll <i>int</i></tt><br> - <tt>maxpoll <i>int</i></tt></dt> + <dt><tt>minpoll <i>int</i></tt></dt> + <dt><tt>maxpoll <i>int</i></tt></dt> <dd>These options specify the minimum and maximum polling interval for reference clock messages in log<sub>2</sub> seconds. For most directly connected reference clocks, both <tt>minpoll</tt> and <tt>maxpoll</tt> default to 6 (64 s). For modem reference clocks, <tt>minpoll</tt> is ordinarily set to 10 (about 17 m) and <tt>maxpoll</tt> to 15 (about 9 h). The allowable range is 4 (16 s) to 17 (36 h) inclusive.</dd> </dl> </dd> @@ -48,7 +48,10 @@ <dd>Specifies the stratum number assigned to the driver in the range 0 to 15, inclusive. This number overrides the default stratum number ordinarily assigned by the driver itself, usually zero.</dd> <dt><tt>refid <i>string</i></tt></dt> <dd>Specifies an ASCII string of from one to four characters which defines the reference identifier used by the driver. This string overrides the default identifier ordinarily assigned by the driver itself.</dd> - <dt><tt>flag1 flag2 flag3 flag4</tt></dt> + <dt><tt>flag1 0|1</tt></dt> + <dt><tt>flag2 0|1</tt></dt> + <dt><tt>flag3 0|1</tt></dt> + <dt><tt>flag4 0|1</tt></dt> <dd>These four flags are used for customizing the clock driver. The interpretation of these values, and whether they are used at all, is a function of the particular driver. However, by convention <tt>flag4</tt> is used to enable recording monitoring data to the <tt>clockstats</tt> file configured with the <tt>filegen</tt> command. Additional information on the <tt>filegen</tt> command is on the <a href="monopt.html">Monitoring Options</a> page.</dd> <dt><tt>minjitter <i>secs</i></tt></dt> <dd>If the source has a jitter that cannot be sensibly estimated, because diff --git a/html/copyright.html b/html/copyright.html index d00cf9712178..7584aefc3230 100644 --- a/html/copyright.html +++ b/html/copyright.html @@ -9,7 +9,7 @@ <h3>Copyright Notice</h3> <img src="pic/sheepb.jpg" alt="jpg" align="left"> "Clone me," says Dolly sheepishly. <p>Last update: - <!-- #BeginDate format:En2m -->2-Mar-2023 05:21<!-- #EndDate --> + <!-- #BeginDate format:En2m -->7-Jan-2024 00:29<!-- #EndDate --> UTC</p> <br clear="left"> </p> @@ -38,7 +38,7 @@ <pre> *********************************************************************** * * -* Copyright (c) Network Time Foundation 2011-2023 * +* Copyright (c) Network Time Foundation 2011-2024 * * * * All Rights Reserved * * * diff --git a/html/release.html b/html/release.html index f940603a0947..d354ba653953 100644 --- a/html/release.html +++ b/html/release.html @@ -37,7 +37,7 @@ <li>There are two new burst mode features available where special conditions apply. One of these is enabled by the <tt>iburst</tt> keyword in the <tt>server</tt> configuration command. It is intended for cases where it is important to set the clock quickly when an association is first mobilized. The other is enabled by the <tt>burst</tt> keyword in the <tt>server</tt> configuration command. It is intended for cases where the network attachment requires an initial calling or training procedure. See the <a href="assoc.html">Association Management</a> page for further information.</li> <li>The OpenSSL cryptographic library has replaced the library formerly available from RSA Laboratories. All cryptographic routines except a version of the MD5 message digest algorithm have been removed from the base distribution. All 128-bit and 160-bit message digests algorithms are now supported for both symmetric key and public key cryptosystems. See the <a href="authentic.html">Authentication Support</a> page for further information and the <a href="authopt.html">Authentication Options</a> page for a list of supported digest algorithms.</li> <li>This release includes support for Autokey public-key cryptography for authenticating public servers to clients, as described in RFC 5906. This support requires the --enable-autokey option when building the distribution, which is the default is OpenSSL is available. The deployment of Autokey subnets is now considerably simpler than in earlier versions. A subnet naming scheme is now available to filter manycast and pool configurations. Additional information about Autokey is on the <a href="autokey.html">Autokey Public Key Authentication</a> page and links from there.</li> - <li>The NTP descrete even simulator has been substantially upgraded, now including scenarios with multiple servers and time-sensitive scripts. This allows the NTP algorithms to be tested in an embedded environment with systematic and pseudo-random network delay and oscillator wander distributions. This has been used to verify correct operation under conditions of extreme error and misconfiguration. See the <a href="ntpdsim.html"><tt>ntpdsim</tt> - Network Time Protocol (NTP) simulator</a> page. A technical description and performance analysis is given in the white papers at the <a href="http://www.eecis.udel.edu/~mills/ntp.html">NTP Project Page</a>.</li> + <li>The NTP descrete event simulator has been substantially upgraded, now including scenarios with multiple servers and time-sensitive scripts. This allows the NTP algorithms to be tested in an embedded environment with systematic and pseudo-random network delay and oscillator wander distributions. This has been used to verify correct operation under conditions of extreme error and misconfiguration. See the <a href="ntpdsim.html"><tt>ntpdsim</tt> - Network Time Protocol (NTP) simulator</a> page. A technical description and performance analysis is given in the white papers at the <a href="http://www.eecis.udel.edu/~mills/ntp.html">NTP Project Page</a>.</li> <li>NTPv4 includes three new server discovery schemes, which in most applications can avoid per-host configuration altogether. Two of these are based on IP multicast technology, while the remaining one is based on crafted DNS lookups. See the <a href="discover.html">Automatic NTP Configuration Schemes</a> page for further information.</li> <li>The status display and event report monitoring functions have been considerably expanded, including new statistics files and event reporting to files and the system log. See the <a href="decode.html">Event Messages and Status Words</a> page for further information.</li> <li>Several new options have been added for the <tt>ntpd</tt> command line. For the inveterate knob twiddlers several of the more important performance variables can be changed to fit actual or perceived special conditions. In particular, the <tt>tinker</tt> and <tt>tos</tt> commands can be used to adjust thresholds, throw switches and change limits.</li> |