![[BACK]](/icons/cvsweb/back.gif){kind=icon}
Return to ntpq.html CVS log ![[TXT]](/icons/cvsweb/text.gif){kind=icon}
![[DIR]](/icons/cvsweb/dir.gif){kind=icon}
Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / ntp / html|
Return to ntpq.html CVS log | Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / ntp / html |
1.1 misho 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2:
3: <html>
4:
5: <head>
6: <meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
7: <meta name="generator" content="HTML Tidy, see www.w3.org">
8: <title>ntpq - standard NTP query program</title>
9: <link href="scripts/style.css" type="text/css" rel="stylesheet">
10: </head>
11:
12: <body>
13: <h3><tt>ntpq</tt> - standard NTP query program</h3>
14: <img src="pic/bustardfly.gif" alt="gif" align="left"><a href="http://www.eecis.udel.edu/~mills/pictures.html">from <i>Pogo</i>, Walt Kelly</a>
15: <p>A typical NTP monitoring packet</p>
16: <p>Last update:
17: <!-- #BeginDate format:En2m -->04-Nov-2009 0:12<!-- #EndDate -->
18: UTC</p>
19: <br clear="left">
20: <h4>More Help</h4>
21: <script type="text/javascript" language="javascript" src="scripts/manual.txt"></script>
22: <hr>
23: <h4>Synopsis</h4>
24: <tt>ntpq [-46dinp] [-c <i>command</i>] [<i>host</i>] [...]</tt>
25: <h4>Description</h4>
26: <p>The <tt>ntpq</tt> utility program is used to monitor NTP daemon <tt>ntpd</tt> operations
27: and determine performance. It uses the standard NTP mode 6 control
28: message formats defined in Appendix B of the NTPv3 specification
29: RFC1305. The same formats are used in NTPv4, although some of the
30: variable names have changed and new ones added. The description
31: on this page is for the NTPv4 variables.</p>
32: <p>The program can be run either in interactive mode or controlled using command line arguments. Requests to read and write arbitrary variables can be assembled, with raw and pretty-printed output options being available. The <tt>ntpq</tt> can also obtain and print a list of peers in a common format by sending multiple queries to the server.</p>
33: <p>If one or more request options is included on the command line when <tt>ntpq</tt> is executed, each of the requests will be sent to the NTP servers running on each of the hosts given as command line arguments, or on localhost by default. If no request options are given, <tt>ntpq</tt> will attempt to read commands from the standard input and execute these on the NTP server running on the first host given on the command line, again defaulting to localhost when no other host is specified. <tt>ntpq</tt> will prompt for commands if the standard input is a terminal device.</p>
34: <p><tt>ntpq</tt> uses NTP mode 6 packets to communicate with the NTP server, and hence can be used to query any compatible server on the network which permits it. Note that since NTP is a UDP protocol this communication will be somewhat unreliable, especially over large distances in terms of network topology. <tt>ntpq</tt> makes one attempt to retransmit requests, and will time requests out if the remote host is not heard from within a suitable timeout time.</p>
35: <p>Note that in contexts where a host name is expected, a <tt>-4</tt> qualifier preceding the host name forces DNS resolution to the IPv4 namespace, while a <tt>-6</tt> qualifier forces DNS resolution to the IPv6 namespace.</p>
36: <p>For examples and usage, see the <a href="debug.html">NTP Debugging Techniques</a> page.</p>
37: <p>Command line options are described following. Specifying a command line option other than <tt>-i</tt> or <tt>-n</tt> will cause the specified query (queries) to be sent to the indicated host(s) immediately. Otherwise, <tt>ntpq</tt> will attempt to read interactive format commands from the standard input.</p>
38: <dl>
39: <dt><tt>-4</tt></dt>
40: <dd>Force DNS resolution of following host names on the command line to the IPv4 namespace.</dd>
41: <dt><tt>-6</tt></dt>
42: <dd>Force DNS resolution of following host names on the command line to the IPv6 namespace.</dd>
43: <dt><tt>-c</tt></dt>
44: <dd>The following argument is interpreted as an interactive format command and is added to the list of commands to be executed on the specified host(s). Multiple <tt>-c</tt> options may be given.</dd>
45: <dt><tt>-d</tt></dt>
46: <dd>Turn on debugging mode.</dd>
47: <dt><tt>-i</tt></dt>
48: <dd>Force <tt>ntpq</tt> to operate in interactive mode. Prompts will be written to the standard output and commands read from the standard input.</dd>
49: <dt><tt>-n</tt></dt>
50: <dd>Output all host addresses in dotted-quad numeric format rather than converting to the canonical host names.</dd>
51: <dt><tt>-p</tt></dt>
52: <dd>Print a list of the peers known to the server as well as a summary of their state. This is equivalent to the <tt>peers</tt> interactive command.</dd>
53: </dl>
54: <h4>Internal Commands</h4>
55: <p>Interactive format commands consist of a keyword followed by zero to four arguments. Only enough characters of the full keyword to uniquely identify the command need be typed. The output of a command is normally sent to the standard output, but optionally the output of individual commands may be sent to a file by appending a <tt>></tt>, followed by a file name, to the command line. A number of interactive format commands are executed entirely within the <tt>ntpq</tt> program itself and do not result in NTP mode-6 requests being sent to a server. These are described following.</p>
56: <dl>
57: <dt><tt>? [<i>command_keyword</i>]</tt><br>
58: <tt>help [<i>command_keyword</i>]</tt></dt>
59: <dd>A <tt>?</tt> by itself will print a list of all the command keywords known to <tt>ntpq</tt>. A <tt>?</tt> followed by a command keyword will print function and usage information about the command.</dd>
60: <dt><tt>addvars <i>name</i> [ = <i>value</i>] [...]</tt><br>
61: <tt>rmvars <i>name</i> [...]</tt><br>
62: <tt>clearvars</tt></dt>
63: <dd>The arguments to this command consist of a list of items of the form <tt><i>name</i> = <i>value</i></tt>, where the <tt>= <i>value</i></tt> is ignored, and can be omitted in read requests. <tt>ntpq</tt> maintains an internal list in which data to be included in control messages can be assembled, and sent using the <tt>readlist</tt> and <tt>writelist</tt> commands described below. The <tt>addvars</tt> command allows variables and optional values to be added to the list. If more than one variable is to be added, the list should be comma-separated and not contain white space. The <tt>rmvars</tt> command can be used to remove individual variables from the list, while the <tt>clearlist</tt> command removes all variables from the list.</dd>
64: <dt><tt>cooked</tt></dt>
65: <dd>Display server messages in prettyprint format.</dd>
66: <dt><tt>debug more | less | off</tt></dt>
67: <dd>Turns internal query program debugging on and off.</dd>
68: <dt><tt>delay <i>milliseconds</i></tt></dt>
69: <dd>Specify a time interval to be added to timestamps included in requests which require authentication. This is used to enable (unreliable) server reconfiguration over long delay network paths or between machines whose clocks are unsynchronized. Actually the server does not now require timestamps in authenticated requests, so this command may be obsolete.</dd>
70: <dt><tt>host <i>name</i></tt></dt>
71: <dd>Set the host to which future queries will be sent. The name may be either a DNS name or a numeric address.</dd>
72: <dt><tt>hostnames [yes | no]</tt></dt>
73: <dd>If <tt>yes</tt> is specified, host names are printed in information displays. If <tt>no</tt> is specified, numeric addresses are printed instead. The default is <tt>yes</tt>, unless modified using the command line <tt>-n</tt> switch.</dd>
74: <dt><tt>keyid <i>keyid</i></tt></dt>
75: <dd>This command specifies the key number to be used to authenticate configuration requests. This must correspond to a key number the server has been configured to use for this purpose.</dd>
76: <dt><tt>ntpversion 1 | 2 | 3 | 4</tt></dt>
77: <dd>Sets the NTP version number which <tt>ntpq</tt> claims in packets. Defaults to 2, Note that mode-6 control messages (and modes, for that matter) didn't exist in NTP version 1.</dd>
78: <dt><tt>passwd</tt></dt>
79: <dd>This command prompts for a password to authenticate configuration requests. The password must correspond to the key configured for NTP server for this purpose.</dd>
80: <dt><tt>quit</tt></dt>
81: <dd>Exit <tt>ntpq</tt>.</dd>
82: <dt><tt>raw</tt></dt>
83: <dd>Display server messages as received and without reformatting.</dd>
84: <dt><tt>timeout <i>milliseconds</i></tt></dt>
85: <dd>Specify a timeout period for responses to server queries. The default is about 5000 milliseconds. Note that since <tt>ntpq</tt> retries each query once after a timeout, the total waiting time for a timeout will be twice the timeout value set.</dd>
86: </dl>
87: <h4>Control Message Commands</h4>
88: <p>Association IDs are used to identify system, peer and clock variables. System variables are assigned an association ID of zero and system name space, while each association is assigned a nonzero association ID and peer namespace. Most control commands send a single mode-6 message to the server and expect a single response message. The exceptions are the <tt>peers</tt> command, which sends a series of messages, and the <tt>mreadlist</tt> and <tt>mreadvar</tt> commands, which iterate over a range of associations.</p>
89: <dl>
90: <dt id="as"><tt>associations</tt></dt>
91: <dd>Display a list of mobilized associations in the form</dd>
92: <dd><tt>ind assid status conf reach auth condition last_event cnt</tt></dd>
93: <dd>
94: <table width="100%" border="1" cellspacing="2" cellpadding="2">
95: <tr>
96: <td>Variable</td>
97: <td>Description</td>
98: </tr>
99: <tr>
100: <td><tt>ind</tt></td>
101: <td>index on this list</td>
102: </tr>
103: <tr>
104: <td><tt>assid</tt></td>
105: <td>association ID</td>
106: </tr>
107: <tr>
108: <td><tt>status</tt></td>
109: <td><a href="decode.html#peer">peer status word</a></td>
110: </tr>
111: <tr>
112: <td><tt>conf</tt></td>
113: <td><tt>yes</tt>: persistent, <tt>no</tt>: ephemeral</td>
114: </tr>
115: <tr>
116: <td><tt>reach</tt></td>
117: <td><tt>yes</tt>: reachable, <tt>no</tt>: unreachable</td>
118: </tr>
119: <tr>
120: <td><tt>auth</tt></td>
121: <td><tt>ok</tt>, <tt>yes</tt>, <tt>bad</tt> and <tt>none</tt></td>
122: </tr>
123: <tr>
124: <td><tt>condition</tt></td>
125: <td>selection status (see the <tt>select</tt> field of the <a href="decode.html#peer">peer status word</a>)</td>
126: </tr>
127: <tr>
128: <td><tt>last_event</tt></td>
129: <td>event report (see the <tt>event</tt> field of the <a href="decode.html#peer">peer status word</a>)</td>
130: </tr>
131: <tr>
132: <td><tt>cnt</tt></td>
133: <td>event count (see the <tt>count</tt> field of the <a href="decode.html#peer">peer status word</a>)</td>
134: </tr>
135: </table>
136: </dd>
137: <dt><tt>clockvar <i>assocID</i> [<i>name</i> [ = <i>value</i> [...]] [...]</tt><br>
138: <tt>cv <i>assocID</i> [<i>name</i> [ = <i>value</i> [...] ][...]</tt></dt>
139: <dd>Display a list of <a href="#clock">clock variables</a> for those assocations supporting a reference clock.</dd>
140: <dt><tt>:config [...]</tt></dt>
141: <dd>Send the remainder of the command line, including whitespace, to the server as a run-time configuration command in the same format as the configuration file. This command is experimental until further notice and clarification. Authentication is of course required.</dd>
142: <dt><tt>config-from-file <i>filename</i></tt></dt>
143: <dd>Send the each line of <i>filename</i> to the server as run-time configuration commands in the same format as the configuration file. This command is experimental until further notice and clarification. Authentication is of course required.</dd>
144: <dt><tt>keyid</tt></dt>
145: <dd>Specify the key ID to use for write requests.</dd>
146: <dt><tt>lassociations</tt></dt>
147: <dd>Perform the same function as the associations command, execept display mobilized and unmobilized associations.</dd>
148: <dt><tt>mreadvar <i>assocID</i> <i>assocID</i> [ <i>variable_name</i> [ = <i>value</i>[ ... ]</tt><br>
149: <tt>mrv <i>assocID</i> <i>assocID</i> [ <i>variable_name</i> [ = <i>value</i>[ ... ]</tt></dt>
150: <dd>Perform the same function as the <tt>readvar</tt> command, except for a range of association IDs. This range is determined from the association list cached by the most recent <tt>associations</tt> command.</dd>
151: <dt><tt>passociations</tt></dt>
152: <dd>Perform the same function as the <tt>associations command</tt>, except that it uses previously stored data rather than making a new query.</dd>
153: <dt><tt>passwd</tt></dt>
154: <dd>Specify the password to use for write requests.</dd>
155: <dt id="pe"><tt>peers</tt></dt>
156: <dd>Display a list of peers in the form</dd>
157: <dd><tt>[tally]remote refid st t when pool reach delay offset jitter</tt></dd>
158: <dd>
159: <table width="100%" border="1" cellspacing="2" cellpadding="2">
160: <tr>
161: <td>Variable</td>
162: <td>Description</td>
163: </tr>
164: <tr>
165: <td><tt>[tally]</tt></td>
166: <td>single-character code indicating current value of the <tt>select</tt> field of the <a href="decode.html#peer">peer status word</a></td>
167: </tr>
168: <tr>
169: <td><tt>remote</tt></td>
170: <td>host name (or IP number) of peer</td>
171: </tr>
172: <tr>
173: <td><tt>refid</tt></td>
174: <td>association ID or <a href="decode.html#kiss">kiss code</a></td>
175: </tr>
176: <tr>
177: <td><tt>st</tt></td>
178: <td>stratum</td>
179: </tr>
180: <tr>
181: <td><tt>t</tt></td>
182: <td><tt>u</tt>: unicast, <tt>b</tt>: broadcast, <tt>l</tt>: local</td>
183: </tr>
184: <tr>
185: <td><tt>when</tt></td>
186: <td>sec/min/hr since last received packet</td>
187: </tr>
188: <tr>
189: <td><tt>poll</tt></td>
190: <td>poll interval (log<sub>2</sub> s)</td>
191: </tr>
192: <tr>
193: <td><tt>reach</tt></td>
194: <td>reach shift register (octal)</td>
195: </tr>
196: <tr>
197: <td><tt>delay</tt></td>
198: <td>roundtrip delay</td>
199: </tr>
200: <tr>
201: <td><tt>offset</tt></td>
202: <td>offset</td>
203: </tr>
204: <tr>
205: <td><tt>jitter</tt></td>
206: <td>jitter</td>
207: </tr>
208: </table>
209: </dd>
210: <dt id="rv"><tt>readvar <i>assocID</i> <i>name</i> [ = <i>value</i> ] [,...]</tt><br>
211: <tt>rv <i>assocID</i> [ <i>name</i> ] [,...]</tt></dt>
212: <dd>Display the specified variables. If <tt><i>assocID</i></tt> is zero, the
213: variables are from the <a href="#system">system variables</a> name space,
214: otherwise they are from the <a href="#peer">peer variables</a> name space.
215: The <tt><i>assocID</i></tt> is required, as the same name can occur in both spaces. If no <tt><i>name</i></tt> is
216: included, all operative variables in the name space are displayed.
217: In this case only, if the <tt><i>assocID</i></tt> is omitted, it is assumed zero. Multiple
218: names are specified with comma separators and without whitespace.
219: Note that time values are represented in milliseconds and frequency
220: values in parts-per-million (PPM). Some NTP timestamps are represented
221: in the format YYYYMMDDTTTT, where YYYY is the year, MM the month
222: of year, DD the day of month and TTTT the time of day.</dd>
223: <dt id="saveconfig"><tt>saveconfig <i>filename</i></tt></dt>
224: <dd>Write the current configuration, including any runtime modifications given with <tt>:config</tt> or <tt>config-from-file</tt>, to the ntpd host's file <i>filename</i>. This command will be rejected by the server unless <a href="miscopt.html#saveconfigdir">saveconfigdir</a> appears in the <tt>ntpd</tt> configuration file. <i>filename</i> can use strftime() format specifiers to substitute the current date and time, for example, <tt>saveconfig ntp-%Y%m%d-%H%M%S.conf</tt>. The filename used is stored in system variable <tt>savedconfig</tt>. Authentication is required.</dd>
225: <dt><tt>writevar <i>assocID</i> <i>name</i> = <i>value</i> [,...]</tt></dt>
226: <dd>Write the specified variables. If the <tt><i>assocID</i></tt> is zero, the variables
227: are from the <a href="#system">system variables</a> name space, otherwise they are from the <a href="#peer">peer variables</a> name space. The <tt><i>assocID</i></tt> is required, as the same name can occur
228: in both spaces.</dd>
229: </dl>
230: <h4 id="status">Status Words and Kiss Codes</h4>
231: <p>The current state of the operating program is shown in a set of status words maintained by the system and each association separately. These words are displayed in the <tt>rv</tt> and <tt>as</tt> commands both in hexadecimal and decoded short tip strings. The codes, tips and short explanations are on the <a href="decode.html">Event Messages and Status Words</a> page. The page also includes a list of system and peer messages, the code for the latest of which is included in the status word.</p>
232: <p>Information resulting from protocol machine state transitions is displayed using an informal set of ASCII strings called <a href="decode.html#kiss">kiss codes</a>. The original purpose was for kiss-o'-death (KoD) packets sent by the server to advise the client of an unusual condition. They are now displayed, when appropriate, in the reference identifier field in various billboards.</p>
233: <h4 id="system">System Variables</h4>
234: <p>The following system variables appear in the <tt>rv</tt> billboard. Not all variables are displayed in some configurations.</p>
235: <table width="100%" border="1" cellspacing="2" cellpadding="2">
236: <tr>
237: <td>Variable</td>
238: <td>Description</td>
239: </tr>
240: <tr>
241: <td><tt>status</tt></td>
242: <td><a href="decode.html#sys">system status word</a></td>
243: </tr>
244: <tr>
245: <td><tt>version</tt></td>
246: <td>NTP software version and build time</td>
247: </tr>
248: <tr>
249: <td><tt>processor</tt></td>
250: <td>hardware platform and version</td>
251: </tr>
252: <tr>
253: <td><tt>system</tt></td>
254: <td>operating system and version</td>
255: </tr>
256: <tr>
257: <td><tt>leap</tt></td>
258: <td>leap warning indicator (0-3)</td>
259: </tr>
260: <tr>
261: <td><tt>stratum</tt></td>
262: <td>stratum (1-15)</td>
263: </tr>
264: <tr>
265: <td><tt>precision</tt></td>
266: <td>precision (log<sub>2</sub> s)</td>
267: </tr>
268: <tr>
269: <td><tt>rootdelay</tt></td>
270: <td>total roundtrip delay to the primary reference clock</td>
271: </tr>
272: <tr>
273: <td><tt>rootdisp</tt></td>
274: <td>total dispersion to the primary reference clock</td>
275: </tr>
276: <tr>
277: <td><tt>peer</tt></td>
278: <td>system peer association ID</td>
279: </tr>
280: <tr>
281: <td><tt>tc</tt></td>
282: <td>time constant and poll exponent (log<sub>2</sub> s) (3-17)</td>
283: </tr>
284: <tr>
285: <td><tt>mintc</tt></td>
286: <td>minimum time constant (log<sub>2</sub> s) (3-10)</td>
287: </tr>
288: <tr>
289: <td><tt>clock</tt></td>
290: <td>date and time of day</td>
291: </tr>
292: <tr>
293: <td><tt>refid</tt></td>
294: <td>reference ID or <a href="decode.html#kiss">kiss code</a></td>
295: </tr>
296: <tr>
297: <td><tt>reftime</tt></td>
298: <td>reference time</td>
299: </tr>
300: <tr>
301: <td><tt>offset</tt></td>
302: <td>combined time offset</td>
303: </tr>
304: <tr>
305: <td><tt>sys_jitter</tt></td>
306: <td>combined system jitter</td>
307: </tr>
308: <tr>
309: <td><tt>frequency</tt></td>
310: <td>clock frequency offset (PPM)</td>
311: </tr>
312: <tr>
313: <td><tt>clk_wander</tt></td>
314: <td>clock frequency wander (PPM)</td>
315: </tr>
316: <tr>
317: <td><tt>clk_jitter</tt></td>
318: <td>clock jitter</td>
319: </tr>
320: <tr>
321: <td><tt>tai</tt></td>
322: <td>TAI-UTC offset (s)</td>
323: </tr>
324: <tr>
325: <td><tt>leapsec</tt></td>
326: <td>NTP seconds when the next leap second is/was inserted</td>
327: </tr>
328: <tr>
329: <td><tt>expire</tt></td>
330: <td>NTP seconds when the NIST leapseconds file expires</td>
331: </tr>
332: </table>
333: <dl>
334: <dt>The jitter and wander statistics are exponentially-weighted RMS averages.
335: The system jitter is defined in the NTPv4 specification; the
336: clock jitter statistic is computed by the clock discipline module.</dt>
337: <dt>When the NTPv4 daemon is compiled with the OpenSSL software library, additional
338: system variables are displayed, including some or all of the following, depending
339: on the particular Autokey dance:</dt>
340: </dl>
341: <table width="100%" border="1" cellspacing="2" cellpadding="2">
342: <tr>
343: <td>Variable</td>
344: <td>Description</td>
345: </tr>
346: <tr>
347: <td><tt>host</tt></td>
348: <td>Autokey host name</td>
349: </tr>
350: <tr>
351: <td><tt>group</tt></td>
352: <td>Autokey group name</td>
353: </tr>
354: <tr>
355: <td><tt>flags</tt></td>
356: <td>host flags (see Autokey specification)</td>
357: </tr>
358: <tr>
359: <td><tt>digest</tt></td>
360: <td>OpenSSL message digest algorithm</td>
361: </tr>
362: <tr>
363: <td><tt>signature</tt></td>
364: <td>OpenSSL digest/signature scheme</td>
365: </tr>
366: <tr>
367: <td><tt>update</tt></td>
368: <td>NTP seconds at last signature update</td>
369: </tr>
370: <tr>
371: <td><tt>cert</tt></td>
372: <td>certificate subject, issuer and certificate flags</td>
373: </tr>
374: <tr>
375: <td><tt>until</tt></td>
376: <td>NTP seconds when the certificate expires</td>
377: </tr>
378: </table>
379: <h4 id="peer">Peer Variables</h4>
380: <p>The following system variables apear in the <tt>rv</tt> billboard for each association. Not all variables are displayed in some configurations.</p>
381: <table width="100%" border="1" cellspacing="2" cellpadding="2">
382: <tr>
383: <td>Variable</td>
384: <td>Description</td>
385: </tr>
386: <tr>
387: <td><tt>associd</tt></td>
388: <td>association ID</td>
389: </tr>
390: <tr>
391: <td><tt>status</tt></td>
392: <td><a href="decode.html#peer">peer status word</a></td>
393: </tr>
394: <tr>
395: <td><tt>srcadr<br>
396: srcport</tt></td>
397: <td>source (remote) IP address and port</td>
398: </tr>
399: <tr>
400: <td><tt>dstadr<br>
401: dstport</tt></td>
402: <td>destination (local) IP address and port</td>
403: </tr>
404: <tr>
405: <td><tt>leap</tt></td>
406: <td>leap indicator (0-3)</td>
407: </tr>
408: <tr>
409: <td><tt>stratum</tt></td>
410: <td>stratum (0-15)</td>
411: </tr>
412: <tr>
413: <td><tt>precision</tt></td>
414: <td>precision (log<sub>2</sub> s)</td>
415: </tr>
416: <tr>
417: <td><tt>rootdelay</tt></td>
418: <td>total roundtrip delay to the primary reference clock</td>
419: </tr>
420: <tr>
421: <td><tt>rootdisp</tt></td>
422: <td>total root dispersion to the primary reference clock</td>
423: </tr>
424: <tr>
425: <td><tt>refid</tt></td>
426: <td>reference ID or <a href="decode.html#kiss">kiss code</a></td>
427: </tr>
428: <tr>
429: <td><tt>reftime</tt></td>
430: <td>reference time</td>
431: </tr>
432: <tr>
433: <td><tt>reach</tt></td>
434: <td>reach register (octal)</td>
435: </tr>
436: <tr>
437: <td><tt>unreach</tt></td>
438: <td>unreach counter</td>
439: </tr>
440: <tr>
441: <td><tt>hmode</tt></td>
442: <td>host mode (1-6)</td>
443: </tr>
444: <tr>
445: <td><tt>pmode</tt></td>
446: <td>peer mode (1-5)</td>
447: </tr>
448: <tr>
449: <td><tt>hpoll</tt></td>
450: <td>host poll exponent (log<sub>2</sub> s) (3-17)</td>
451: </tr>
452: <tr>
453: <td><tt>ppoll</tt></td>
454: <td>peer poll exponent (log<sub>2</sub> s) (3-17)</td>
455: </tr>
456: <tr>
457: <td><tt>headway</tt></td>
458: <td>headway (see <a href="rate.html">Rate Management and the Kiss-o'-Death Packet)</a></td>
459: </tr>
460: <tr>
461: <td><tt>flash</tt></td>
462: <td><a href="decode.html#flash">flash status word</a></td>
463: </tr>
464: <tr>
465: <td><tt>offset</tt></td>
466: <td>filter offset</td>
467: </tr>
468: <tr>
469: <td><tt>delay</tt></td>
470: <td>filter delay</td>
471: </tr>
472: <tr>
473: <td><tt>dispersion</tt></td>
474: <td>filter dispersion</td>
475: </tr>
476: <tr>
477: <td><tt>jitter</tt></td>
478: <td>filter jitter</td>
479: </tr>
480: <tr>
481: <td><tt>bias</tt></td>
482: <td>unicast/broadcast bias</td>
483: </tr>
484: <tr>
485: <td><tt>xleave</tt></td>
486: <td>interleave delay (see <a href="xleave.html">NTP Interleaved Modes</a>)</td>
487: </tr>
488: </table>
489: <p>The bias vaqriable is calculated when the first broadcast packet is received
490: after the calibration volley. It represents the offset of the broadcast
491: subgraph relative to the unicast subgraph. The xleave variable appears
492: only the interleaved symmetric and ingterleaved modes. It represents
493: the internal queueing, buffering and transmission delays for the preceeding
494: packet.</p>
495: <p>When the NTPv4 daemon is compiled with the OpenSSL software library, additional peer variables are displayed, including the following:</p>
496: <table width="100%" border="1" cellspacing="2" cellpadding="2">
497: <tr>
498: <td>Variable</td>
499: <td>Description</td>
500: </tr>
501: <tr>
502: <td><tt>flags</tt></td>
503: <td>peer flags (see Autokey specification)</td>
504: </tr>
505: <tr>
506: <td><tt>host</tt></td>
507: <td>Autokey server name</td>
508: </tr>
509: <tr>
510: <td><tt>flags</tt></td>
511: <td>peer flags (see Autokey specification)</td>
512: </tr>
513: <tr>
514: <td><tt>signature</tt></td>
515: <td>OpenSSL digest/signature shceme</td>
516: </tr>
517: <tr>
518: <td><tt>initsequence</tt></td>
519: <td>initial key ID</td>
520: </tr>
521: <tr>
522: <td><tt>initkey</tt></td>
523: <td>initial key index</td>
524: </tr>
525: <tr>
526: <td><tt>timestamp</tt></td>
527: <td>Autokey signature timestamp</td>
528: </tr>
529: </table>
530: <h4 id="clock">Clock Variables</h4>
531: <p>The following clock variables apear in the <tt>cv</tt> billboard for each association with a reference clock. Not all variables are displayed in some configurations.</p>
532: <table width="100%" border="1" cellspacing="2" cellpadding="2">
533: <tr>
534: <td>Variable</td>
535: <td>Description</td>
536: </tr>
537: <tr>
538: <td><tt>associd</tt></td>
539: <td>association ID</td>
540: </tr>
541: <tr>
542: <td><tt>status</tt></td>
543: <td><a href="decode.html#clock">clock status word</a></td>
544: </tr>
545: <tr>
546: <td><tt>device</tt></td>
547: <td>device description</td>
548: </tr>
549: <tr>
550: <td><tt>timecode</tt></td>
551: <td>ASCII timecode string (specific to device)</td>
552: </tr>
553: <tr>
554: <td><tt>poll</tt></td>
555: <td>poll messages sent</td>
556: </tr>
557: <tr>
558: <td><tt>noreply</tt></td>
559: <td>no reply</td>
560: </tr>
561: <tr>
562: <td><tt>badformat</tt></td>
563: <td>bad format</td>
564: </tr>
565: <tr>
566: <td><tt>baddata</tt></td>
567: <td>bad date or time</td>
568: </tr>
569: <tr>
570: <td><tt>fudgetime1</tt></td>
571: <td>fudge time 1</td>
572: </tr>
573: <tr>
574: <td><tt>fudgetime2</tt></td>
575: <td>fudge time 2</td>
576: </tr>
577: <tr>
578: <td><tt>stratum</tt></td>
579: <td>driver stratum</td>
580: </tr>
581: <tr>
582: <td><tt>refid</tt></td>
583: <td>driver reference ID</td>
584: </tr>
585: <tr>
586: <td><tt>flags</tt></td>
587: <td>driver flags</td>
588: </tr>
589: </table>
590: <hr>
591: <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
592: </body>
593:
594: </html>