<h3><tt>ntptrace</tt> - trace a chain of NTP servers back to the primary source</h3>
<imgsrc="pic/alice13.gif"alt="gif"align="left"><ahref="http://www.eecis.udel.edu/~mills/pictures.html">from <i>Alice's Adventures in Wonderland</i>, Lewis Carroll</a>
<p>The rabbit knows the way back.</p>
<p>Last update: <csobjformat="ShortTime"h="25"locale="00000409"region="0"t="DateTime"w="61">18:47</csobj> UTC <csobjformat="LongDate"h="25"locale="00000409"region="0"t="DateTime"w="246">Thursday, July 28, 2005</csobj></p>
<p><tt>ntptrace</tt> determines where a given Network Time Protocol (NTP) server gets its time from, and follows the chain of NTP servers back to their master time source. If given no arguments, it starts with <tt>localhost</tt>. Here is an example of the output from <tt>ntptrace</tt>:</p>
<p>On each line, the fields are (left to right): the host name, the host stratum, the time offset between that host and the local host (as measured by <tt>ntptrace</tt>; this is why it is not always zero for "<tt>localhost</tt>"), the host synchronization distance, and (only for stratum-1 servers) the reference clock ID. All times are given in seconds. Note that the stratum is the server hop count to the primary source, while the synchronization distance is the estimated error relative to the primary source. These terms are precisely defined in RFC-1305.</p>
<h4>Options</h4>
<dl>
<dt><tt>-d</tt>
<dd>Turns on some debugging output.
<dt><tt>-n</tt>
<dd>Turns off the printing of host names; instead, host IP addresses are given. This may be useful if a nameserver is down.
<dt><tt>-r <i>retries</i></tt>
<dd>Sets the number of retransmission attempts for each host (default = 5).
<dt><tt>-t <i>timeout</i></tt>
<dd>Sets the retransmission timeout (in seconds) (default = 2).
<dt><tt>-v</tt>
<dd>Prints verbose information about the NTP servers.
</dl>
<h4>Bugs</h4>
<p>This program makes no attempt to improve accuracy by doing multiple samples.</p>
