<img src="pic/barnstable.gif" alt="gif" align="left"><a href="http://www.eecis.udel.edu/%7emills/pictures.html"><i>P.T. Bridgeport Bear</i>; from <i>Pogo</i>, Walt Kelly</a>
<p>Pleased to meet you.</p>
<p>Last update:
- <!-- #BeginDate format:En2m -->11-Sep-2010 21:04<!-- #EndDate -->
+ <!-- #BeginDate format:En2m -->11-Nov-2011 1:25<!-- #EndDate -->
UTC</p>
<br clear="left">
<h4>Related Links</h4>
<dd>It is very important that readers understand that the NTP document collection began 25 years ago and remains today a work in progress. It has evolved as new features were invented and old features retired. It has been widely copied, cached and morphed to other formats, including man pages, with varying loss of fidelity. However, these HTML pages are the ONLY authoritative and definitive reference. Readers should always use the collection that comes with the distribution they use. A copy of the online collection at <a href="http://www.ntp.org">www.ntp.org</a> is normally included in the most recent snapshot, but might not agree with an earlier snapshot or release version.</dd>
</dl>
<p>This distribution is an implementation of RFC-5905 "Network Time Protocol Version 4: Protocol and Algorithms Specification".<br>
- NTP is widely used to synchronize a computer to Internet time servers or other sources, such as a radio or satellite receiver or telephone modem service. It can also be used as a serverfor dependent clients. It provides accuracies typically less than a millisecond on LANs and up to a few milliseconds on WANs. Typical NTP configurations utilize multiple redundant servers and diverse network paths in order to achieve high accuracy and reliability.</p>
+ NTP is widely used to synchronize a computer to Internet time servers or other sources, such as a radio or satellite receiver or telephone modem service. It can also be used as a server for dependent clients. It provides accuracies typically less than a millisecond on LANs and up to a few milliseconds on WANs. Typical NTP configurations utilize multiple redundant servers and diverse network paths in order to achieve high accuracy and reliability.</p>
<p>This distribution includes a simulation framework in which substantially all the runtime NTP operations and most features can be tested and evaluated. This has been very useful in exploring in vitro response to unusual circumstances or over time periods impractical in vivo. Details are on the <a href="ntpdsim.html">Network Time Protocol (NTP) Simulator</a> page.</p>
<h4 id="hand">The Handbook</h4>
-<p>A good deal of tutorial and directive information is availabl on the handbook pages. These should be read in conjunction with the command and opetion information available on the pages listed on the sitemap page.</p>
+<p>A good deal of tutorial and directive information is available on the handbook pages. These should be read in conjunction with the command and option information available on the pages listed on the sitemap page.</p>
<dl>
- <dt><a href="release.html">NTP Version 4 Release NotesVersion 4 Release Notes</a></dt>
+ <dt><a href="release.html">NTP Version 4 Release Notes</a></dt>
<dd>Lists recent changes and new features in the current distribution.</dd>
<dt><a href="assoc.html">Association Management</a></dt>
<dd>Describes how to configure servers and peers and manage the various options. Includes automatic server discovery schemes.</dd>
<dt><a href="discover.html">Automatic Server Discovery Schemes</a></dt>
- <dd>Describes automatic ser very discovery using broadcast, multicast, manycast and server pool scheme.</dd>
+ <dd>Describes automatic server discovery using broadcast, multicast, manycast and server pool scheme.</dd>
<dt><a href="access.html">Access Control Support</a></dt>
<dd>Describes the access control mechanisms that can be used to limit client access to various time and management functions.</dd>
<dt><a href="authentic.html">Authentication Support</a></dt>
<dd>Describes the authentication mechanisms for symmetric-key and public-key cryptography.</dd>
<dt><a href="rate.html">Rate Management</a></dt>
- <dd>Describes the principles of rate management to minimize network load and defend against DoS attacks</dd>
+ <dd>Describes the principles of rate management to minimize network load and defend against DoS attacks.</dd>
<dt> </dt>
<dt><a href="refclock.html">Reference Clock Support</a></dt>
<dd>Describes the collection of radio clocks used to synchronize primary servers.</dd>
<dd>Gives an overview of the NTP daemon architecture and how it works.</dd>
</dl>
<h4 id="build">Building and Installing NTP</h4>
-<p>NTP supports Unix, VMS and Windows (Vista, XP,
NT4 and 2000) systems. The <a href="build.html">Building and Installing the Distribution</a> page details the procedures for building and installing on a typical system. This distribution includes drivers for 44 radio and satellite receivers and telephone modem services in the US, Canada and Europe. A list of supported drivers is on the <a href="refclock.html">Reference Clock Drivers</a> page. The default build includes the debugging options and all drivers that run on the target machine; however, options and drivers can be included or excluded using options on the <a href="config.html">Configuration Options</a> page.</p>
+<p>NTP supports Unix, VMS and Windows (Vista, XP,
Windows 7, NT4 and 2000) systems. The <a href="build.html">Building and Installing the Distribution</a> page details the procedures for building and installing on a typical system. This distribution includes drivers for many radio and satellite receivers and telephone modem services in the US, Canada and Europe. A list of supported drivers is on the <a href="refclock.html">Reference Clock Drivers</a> page. The default build includes the debugging options and all drivers that run on the target machine; however, options and drivers can be included or excluded using options on the <a href="config.html">Configuration Options</a> page.</p>
<h4 id="prob">Resolving Problems</h4>
-<p>Like other things in modern Internet life, NTP problems can be devilishly intricate. This distribution includes a number of utilities designed to identify and repair problems using an integrated management protocol supported by the <a href="ntpq.html"><tt>ntpq</tt></a> utility program In addition, the <a href="ntpdc.html"><tt>ntpdc</tt></a> utility program can be useful in some cases.</p>
+<p>Like other things in modern Internet life, NTP problems can be devilishly intricate. This distribution includes a number of utilities designed to identify and repair problems using an integrated management protocol supported by the <a href="ntpq.html"><tt>ntpq</tt></a> utility program. </p>
<p>The <a href="debug.html">NTP Debugging Techniques</a> and <a href="hints.html">Hints and Kinks</a> pages contain useful information for identifying problems and devising solutions. Additional information on reference clock driver construction and debugging is in the <a href="rdebug.html">Debugging Hints for Reference Clock Drivers</a> page.</p>
<p>Users are invited to report bugs and offer suggestions via the <a href="bugs.html">NTP Bug Reporting Procedures</a> page.</p>
<h4 id="info">Further Information</h4>
<img src="pic/boom4.gif" alt="gif" align="left"><a href="http://www.eecis.udel.edu/%7emills/pictures.html">from <i>Pogo</i>, Walt Kelly</a>
<p>Our junior managers and the administrators.</p>
<p>Last update:
- <!-- #BeginDate format:En2m -->26-Oct-2011 18:12<!-- #EndDate -->
+ <!-- #BeginDate format:En2m -->06-Nov-2011 20:00<!-- #EndDate -->
UTC</p>
<br clear="left">
<h4>Related Links</h4>
<p> In order to make sure the client notices the KoD packet, the server sets the receive and transmit timestamps to the transmit timestamp of the client packet. Thus, even if the client ignores all except the timestamps, it cannot do any useful time computations. KoD packets themselves are rate limited to no more than one packet per guard time, in order to defend against flood attacks.</p>
<h4 id="ref">References</h4>
<ol>
-<li>Mills, D.L., J. Levine, R. Schmidt and D. Plonka. Coping with overload on the Network Time Protocol public servers. <i>Proc. Precision Time and Time Interval (PTTI) Applications and Planning Meeting</i> (Washington DC, December 2004), 5-16. Paper: <a href="database/papers/ptti/ptti04a.pdf">PDF</a>, Slides:<a href="database/brief/ptti/ptti04.pdf">PDF</a> | <a href="database/brief/ptti/ptti04.ppt">PowerPoint</a></li>
+<li>Mills, D.L., J. Levine, R. Schmidt and D. Plonka. Coping with overload on the Network Time Protocol public servers. <i>Proc. Precision Time and Time Interval (PTTI) Applications and Planning Meeting</i> (Washington DC, December 2004), 5-16. Paper: <a href="http://www.eecis.udel.edu/~mills/database/papers/ptti/ptti04a.pdf">PDF</a>, Slides:<a href="http://www.eecis.udel.edu/~mills/database/brief/ptti/ptti04.pdf">PDF</a> | <a href="http://www.eecis.udel.edu/~mills/database/brief/ptti/ptti04.ppt">PowerPoint</a></li>
</ol>
<hr>
<script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
projects / thirdparty / ntp.git / commitdiff
