ntpq.texi revision 330106
1\input texinfo @c -*-texinfo-*- 2@c %**start of header 3@setfilename ntpq.info 4@settitle ntpq: Network Time Protocol Query User's Manual 5@include ../sntp/include/version.texi 6@paragraphindent 2 7@c %**end of header 8 9@ifinfo 10This file documents the use of the NTP Project's ntpq, a program for 11querying the state of an NTP server. 12@end ifinfo 13 14@direntry 15* ntpq: (ntpq). NTP Query program 16@end direntry 17 18@titlepage 19@title ntpq: Network Time Protocol Query User's Manual 20@subtitle ntpq, version @value{VERSION}, @value{UPDATED} 21@c @author Max @email{foo@ntp.org} 22@end titlepage 23 24@c @page 25@c @vskip 0pt plus 1filll 26 27@shortcontents 28 29@node Top, ntpq Description, (dir), (dir) 30@top ntpq: Network Time Protocol Query User Manual 31 32The @code{ntpq} utility program is used to 33monitor the operational status 34and determine the performance of 35@code{ntpd}, the NTP daemon. 36 37This document applies to version @value{VERSION} of @code{ntpq}. 38 39@menu 40* ntpq Description:: 41* ntpq Invocation:: Invoking ntpq 42* Usage:: 43* Internal Commands:: 44* Control Message Commands:: 45* Status Words and Kiss Codes:: 46* System Variables:: 47* Peer Variables:: 48* Clock Variables:: 49@end menu 50 51@node ntpq Description, Usage, Top, Top 52@comment node-name, next, previous, up 53@section Description 54 55The @code{ntpq} utility program is used to monitor NTP daemon @code{ntpd} operations and determine performance. 56It uses the standard NTP mode 6 control message formats defined in 57Appendix B of the NTPv3 specification RFC1305. 58The same formats are used in NTPv4, although some of the variable names have changed and new ones added. 59The description on this page is for the NTPv4 variables. 60 61The 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 @code{ntpq} can also obtain and print a list of peers in a common format by sending multiple queries to the server. 62 63If one or more request options is included on the command line when @code{ntpq} 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, @code{ntpq} 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. @code{ntpq} will prompt for commands if the standard input is a terminal device. 64 65@code{ntpq} 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. @code{ntpq} makes one attempt to retransmit requests, and will time requests out if the remote host is not heard from within a suitable timeout time. 66 67Note that in contexts where a host name is expected, a @code{-4} qualifier preceding the host name forces DNS resolution to the IPv4 namespace, while a @code{-6} qualifier forces DNS resolution to the IPv6 namespace. 68 69For examples and usage, see the @url{debug.html, NTP Debugging Techniques} page. 70 71@include invoke-ntpq.texi 72 73@node Usage, Internal Commands, ntpq Description, Top 74@comment node-name, next, previous, up 75@section Usage 76 77@multitable @columnfractions .23 .23 .05 .15 78@headitem What @tab Default @tab Flag @tab Option 79@item configuration file 80@tab @code{/etc/ntp.conf} 81@tab @code{-c} 82@tab @code{conffile} 83@item frequency file 84@tab none 85@tab @code{-f} 86@tab @code{driftfile} 87@item leapseconds file 88@tab none 89@tab 90@tab @code{leapfile} 91@item process ID file 92@tab none 93@tab @code{-p} 94@tab @code{pidfile} 95@item log file 96@tab system log 97@tab @code{-l} 98@tab @code{logfile} 99@item include file 100@tab none 101@tab none 102@tab @code{includefile} 103@item statistics path 104@tab @code{/var/NTP} 105@tab @code{-s} 106@tab @code{statsdir} 107@item keys path 108@tab @code{/usr/local/etc} 109@tab @code{-k} 110@tab @code{keysdir} 111@end multitable 112 113@node Internal Commands, Control Message Commands, Usage, Top 114@comment node-name, next, previous, up 115@section Internal Commands 116 117Interactive 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 @code{>}, followed by a file name, to the command line. A number of interactive format commands are executed entirely within the @code{ntpq} program itself and do not result in NTP mode-6 requests being sent to a server. These are described following. 118 119@table @code 120 121@item @anchor{help} @code{? [}@kbd{command_keyword}@code{]} 122@itemx @code{help [}@kbd{command_keyword}@code{]} 123A @code{?} by itself will print a list of all the command keywords known to @code{ntpq}. A @code{?} followed by a command keyword will print function and usage information about the command. 124 125@item @anchor{addvars} >@code{addvars @kbd{name} [ = @kbd{value}] [...]} 126@itemx @code{rmvars @kbd{name} [...]} 127@itemx @code{clearvars}</dt> 128The arguments to these commands consist of a list of items of the form 129@code{@kbd{name} = @kbd{value}}, where the @code{= @kbd{value}} is ignored, 130and can be omitted in read requests. 131@code{ntpq} maintains an internal list in which data to be included 132in control messages can be assembled, and sent using the @code{readlist} 133and @code{writelist} commands described below. 134The @code{addvars} command allows variables and optional values 135to be added to the list. 136If more than one variable is to be added 137the list should be comma-separated and not contain white space. 138The @code{rmvars} command can be used to remove individual variables 139from the list, 140while the @code{clearlist} command removes all variables from the list. 141 142@item @anchor{cooked} @code{cooked} 143Display server messages in prettyprint format. 144 145@item @anchor{debug} @code{debug more | less | off} 146Turns internal query program debugging on and off. 147 148@item @anchor{delay} @code{delay @kbd{milliseconds}} 149Specify 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. 150 151@item @anchor{host} @code{host @kbd{name}} 152Set the host to which future queries will be sent. 153The name may be either a DNS name or a numeric address. 154 155@item @anchor{hostnames} @code{hostnames [yes | no]} 156If @code{yes} is specified, host names are printed in information displays. 157If @code{no} is specified, numeric addresses are printed instead. 158The default is @code{yes}, 159unless modified using the command line @code{-n} switch. 160 161@item @anchor{keyid} @code{keyid @kbd{keyid}} 162This command specifies the key number to be used 163to authenticate configuration requests. 164This must correspond to a key ID configured in @code{ntp.conf} for this purpose. 165 166@item @anchor{keytype} @code{keytype} 167Specify the digest algorithm to use for authenticated requests, 168with default @code{MD5}. 169If the OpenSSL library is installed, 170digest can be be any message digest algorithm supported by the library. 171The current selections are: @code{AES128CMAC}, @code{MD2}, @code{MD4}, @code{MD5}, @code{MDC2}, @code{RIPEMD160}, @code{SHA} and @code{SHA1}. 172 173@item @anchor{ntpversion} @code{ntpversion 1 | 2 | 3 | 4} 174Sets the NTP version number which @code{ntpq} claims in packets. 175Defaults to 2. 176Note that mode-6 control messages (and modes, for that matter) 177didn't exist in NTP version 1. 178 179@item @anchor{passwd} @code{passwd} 180This command prompts for a password to authenticate requests. 181The password must correspond to the key ID configured in @code{ntp.conf} for this purpose. 182 183@item @anchor{quit} @code{quit} 184Exit @code{ntpq}. 185 186@item @anchor{raw} @code{raw} 187Display server messages as received and without reformatting. 188 189@item @anchor{timeout} @code{timeout @kbd{millseconds}} 190Specify a timeout period for responses to server queries. 191The default is about 5000 milliseconds. 192Note that since @code{ntpq} retries each query once after a timeout 193the total waiting time for a timeout will be twice the timeout value set. 194 195@end table 196 197@node Control Message Commands, Status Words and Kiss Codes, Internal Commands, Top 198@comment node-name, next, previous, up 199@section Control Message Commands 200 201Association IDs are used to identify system, peer and clock variables. 202System variables are assigned an association ID of zero and system name space, 203while each association is assigned a nonzero association ID and peer namespace. 204Most control commands send a single mode-6 message to the server 205and expect a single response message. 206The exceptions are the @code{peers} command, 207which sends a series of messages, 208and the @code{mreadlist} and @code{mreadvar} commands, 209which iterate over a range of associations. 210 211@anchor{as} 212@table @code 213@item @code{associations} 214Display a list of mobilized associations in the form: 215@* 216@code{ind assid status conf reach auth condition last_event cnt} 217 218@multitable @columnfractions .1 .4 219@headitem Variable @tab Description 220 221@item @code{ind} 222@tab index on this list 223 224@item @code{assid} 225@tab association ID 226 227@item @code{status} 228@tab @url{decode.html#peer, peer status word} 229 230@item @code{conf} 231@tab @code{yes}: persistent, @code{no}: ephemeral 232 233@item @code{reach} 234@tab @code{yes}: reachable, @code{no}: unreachable 235 236@item @code{auth} 237@tab @code{ok}, @code{yes}, @code{bad} and @code{none} 238 239@item @code{condition} 240@tab selection status (see the @code{select} field of the @url{decode.html#peer, peer status word}) 241 242@item @code{last_event} 243@tab event report (see the @code{event} field of the @url{decode.html#peer, peer status word}) 244 245@item @code{cnt} 246event count (see the @code{count} field of the @url{decode.html#peer, peer status word}) 247 248@end multitable 249 250@item @anchor{cv} clockvar @kbd{assocID} [@kbd{name} [ = @kbd{value} [...]] [...]] 251@itemx cv @kbd{assocID} [@kbd{name} [ = @kbd{value} [...] ][...]] 252Display a list of @ref{clock,,clock variables} for those associations supporting a reference clock. 253 254@item @anchor{:config} :config [...] 255Send the remainder of the command line, including whitespace, to the server 256as a run-time configuration command in the same format 257as the configuration file. 258This command is experimental until further notice and clarification. 259Authentication is of course required. 260 261@item @anchor{config-from-file} config-from-file @kbd{filename} 262Send the each line of @kbd{filename} to the server as 263run-time configuration commands in the same format as the configuration file. 264This command is experimental until further notice and clarification. 265Authentication is required. 266 267@item @anchor{ifstats} ifstats 268Display statistics for each local network address. 269Authentication is required. 270 271@item @anchor{iostats} iostats 272Display network and reference clock I/O statistics. 273 274@item @anchor{kerninfo} kerninfo 275Display kernel loop and PPS statistics. 276As with other ntpq output, times are in milliseconds. 277The precision value displayed is in milliseconds as well, 278unlike the precision system variable. 279 280@item @anchor{lassoc} lassociations 281Perform the same function as the associations command, 282except display mobilized and unmobilized associations. 283 284@item @anchor{monstats} monstats 285Display monitor facility statistics. 286 287@item @anchor{mrulist} mrulist [limited | kod | mincount=@kbd{count} | laddr=@kbd{localaddr} | sort=@kbd{sortorder} | resany=@kbd{hexmask} | resall=@kbd{hexmask}] 288Obtain and print traffic counts collected and maintained by 289the monitor facility. 290With the exception of @code{sort=@kbd{sortorder}}, 291the options filter the list returned by @code{ntpd}. 292The @code{limited} and @code{kod} options return only entries 293representing client addresses from which the last packet received 294triggered either discarding or a KoD response. 295The @code{mincount=@kbd{count}} option filters entries representing 296less than @code{@kbd{count}} packets. 297The @code{laddr=@kbd{localaddr}} option filters entries for packets 298received on any local address other than @code{@kbd{localaddr}}. 299@code{resany=@kbd{hexmask}} and @code{resall=@kbd{hexmask}} 300filter entries containing none or less than all, respectively, 301of the bits in @code{@kbd{hexmask}}, which must begin with @code{0x}. 302@* 303The @code{@kbd{sortorder}} defaults to @code{lstint} and may be any of 304@code{addr}, @code{count}, @code{avgint}, @code{lstint}, or 305any of those preceded by a minus sign (hyphen) to reverse the sort order. 306The output columns are: 307 308@multitable @columnfractions .1 .4 309@headitem Column @tab Description 310 311@item @code{lstint} 312@tab 313Interval in s between the receipt of the most recent packet from this 314address and the completion of the retrieval of the MRU list by @code{ntpq} 315 316@item @code{avgint} 317@tab 318Average interval in s between packets from this address. 319 320@item @code{rstr} 321@tab 322Restriction flags associated with this address. 323Most are copied unchanged from the matching @code{restrict} command, 324however 0x400 (kod) and 0x20 (limited) flags are cleared unless 325the last packet from this address triggered a rate control response. 326 327@item @code{r} 328@tab 329Rate control indicator, either a period, @code{L} or @code{K} for 330no rate control response, rate limiting by discarding, or 331rate limiting with a KoD response, respectively. 332 333@item @code{m} 334@tab 335Packet mode. 336@item @code{v} 337@tab 338Packet version number. 339 340@item @code{count} 341@tab 342Packets received from this address. 343 344@item @code{rport} 345@tab 346Source port of last packet from this address. 347 348@item @code{remote address} 349@tab 350DNS name, numeric address, or address followed by claimed DNS name which 351could not be verified in parentheses. 352 353@end multitable 354 355@item @anchor{mreadvar} @code{mreadvar @kbd{assocID} @kbd{assocID} [ @kbd{variable_name} [ = @kbd{value}[ ... ]} 356@itemx @anchor{mrv} @code{mrv @kbd{assocID} @kbd{assocID} [ @kbd{variable_name} [ = @kbd{value}[ ... ]} 357Perform the same function as the @code{readvar} command, 358except for a range of association IDs. 359This range is determined from the association list cached by 360the most recent @code{associations} command. 361 362@item @anchor{passoc} @code{passociations} 363Perform the same function as the @code{associations command}, except that 364it uses previously stored data rather than making a new query. 365 366@item @anchor{pe} @code{peers} 367Display a list of peers in the form: 368@* 369@code{[tally]remote refid st t when pool reach delay offset jitter} 370 371@multitable @columnfractions .1 .2 372@headitem Variable @tab Description 373@item @code{[tally]} 374@tab 375single-character code indicating current value of the @code{select} field 376of the @url{decode.html#peer, peer status word}. 377 378@item @code{remote} 379@tab 380host name (or IP number) of peer 381 382@item @code{refid} 383@tab 384association ID or @url{decode.html#kiss, kiss code}. 385 386@item @code{st} 387@tab 388stratum 389 390@item @code{t} 391@tab 392@code{u}: unicast or manycast client, 393@code{b}: broadcast or multicast client, 394@code{l}: local (reference clock), 395@code{s}: symmetric (peer), 396@code{A}: manycast server, 397@code{B}: broadcast server, 398@code{M}: multicast server. 399 400@item @code{when} 401@tab 402sec/min/hr since last received packet 403 404@item @code{poll} 405@tab 406poll interval (log(2) s) 407 408@item @code{reach} 409@tab 410reach shift register (octal) 411 412@item @code{delay} 413@tab 414roundtrip delay 415 416@item @code{offset} 417@tab 418offset of server relative to this host 419 420@item @code{jitter} 421@tab 422jitter 423 424@end multitable 425 426@item @anchor{rv} readvar @kbd{assocID} @kbd{name} [ = @kbd{value} ] [,...] 427@itemx rv @kbd{assocID} [ @kbd{name} ] [,...] 428Display the specified variables. 429If @code{@kbd{assocID}} is zero, 430the variables are from the @ref{system, system variables} name space, 431otherwise they are from the @ref{peer, peer variables} name space. 432The @kbd{assocID} is required, as the same name can occur in both spaces. 433If no @kbd{name} is included, 434all operative variables in the name space are displayed. 435In this case only, if the @code{@kbd{assocID}} is omitted, it is assumed zero. 436Multiple names are specified with comma separators and without whitespace. 437Note that time values are represented in milliseconds and 438frequency values in parts-per-million (PPM). 439Some NTP timestamps are represented in the format YYYYMMDDTTTT, 440where YYYY is the year, MM the month of year, DD the day of month and 441TTTT the time of day. 442 443@item @anchor{saveconfig} @code{saveconfig @kbd{filename}} 444Write the current configuration, including any runtime modifications 445given with @code{:config} or @code{config-from-file}, 446to the ntpd host's file @kbd{filename}. 447This command will be rejected by the server unless 448@url{miscopt.html#saveconfigdir, saveconfigdir} 449appears in the @code{ntpd} configuration file. 450@kbd{filename} can use @code{strftime()} format specifiers 451to substitute the current date and time, for example, 452@code{saveconfig ntp-%Y%m%d-%H%M%S.conf}. 453The filename used is stored in system variable @code{savedconfig}. 454Authentication is required. 455 456@item @anchor{writevar} writevar @kbd{assocID} @kbd{name} = @kbd{value} [,...] 457Write the specified variables. 458If the @code{@kbd{assocID}} is zero, the variables are from the 459@ref{system, system variables} name space, otherwise they are from the 460@ref{peer, peer variables} name space. 461The @code{@kbd{assocID}} is required, 462as the same name can occur in both spaces. 463 464@item @anchor{sysinfo} @code{sysinfo} 465Display operational summary. 466 467@item @anchor{sysstats} @code{sysstats} 468Print statistics counters maintained in the protocol module. 469 470@end table 471 472@node Status Words and Kiss Codes, System Variables, Control Message Commands, Top 473@comment node-name, next, previous, up 474@section Status Words and Kiss Codes 475 476The current state of the operating program is shown 477in a set of status words maintained by the system 478and each association separately. 479These words are displayed in the @code{rv} and @code{as} commands 480both in hexadecimal and decoded short tip strings. 481The codes, tips and short explanations are on the 482@url{decode.html, Event Messages and Status Words} page. 483The page also includes a list of system and peer messages, 484the code for the latest of which is included in the status word. 485 486Information resulting from protocol machine state transitions 487is displayed using an informal set of ASCII strings called 488@url{decode.html#kiss, kiss codes}. 489The original purpose was for kiss-o'-death (KoD) packets sent 490by the server to advise the client of an unusual condition. 491They are now displayed, when appropriate, 492in the reference identifier field in various billboards. 493 494@node System Variables, Peer Variables, Status Words and Kiss Codes, Top 495@comment node-name, next, previous, up 496@section System Variables 497 498The following system variables appear in the @code{rv} billboard. 499Not all variables are displayed in some configurations. 500 501@multitable @columnfractions .1 .2 502@headitem Variable @tab Description 503 504@item @code{status} 505@tab 506@url{decode.html#sys, system status word} 507 508@item @code{version} 509@tab 510NTP software version and build time 511 512@item @code{processor} 513@tab 514hardware platform and version 515 516@item @code{system} 517@tab 518operating system and version 519 520@item @code{leap} 521@tab 522leap warning indicator (0-3) 523 524@item @code{stratum} 525@tab 526stratum (1-15) 527 528@item @code{precision} 529@tab 530precision (log(2) s) 531 532@item @code{rootdelay} 533@tab 534total roundtrip delay to the primary reference clock 535 536@item @code{rootdisp} 537@tab 538total dispersion to the primary reference clock 539 540@item @code{peer} 541@tab 542system peer association ID 543 544@item @code{tc} 545time constant and poll exponent (log(2) s) (3-17) 546 547@item @code{mintc} 548minimum time constant (log(2) s) (3-10) 549 550@item @code{clock} 551@tab 552date and time of day 553 554@item @code{refid} 555reference ID or @url{decode.html#kiss, kiss code} 556 557@item @code{reftime} 558@tab 559reference time 560 561@item @code{offset} 562@tab 563combined offset of server relative to this host 564 565@item @code{sys_jitter} 566@tab 567combined system jitter 568 569@item @code{frequency} 570@tab 571frequency offset (PPM) relative to hardware clock 572 573@item @code{clk_wander} 574@tab 575clock frequency wander (PPM) 576 577@item @code{clk_jitter} 578@tab 579clock jitter 580 581@item @code{tai} 582@tab 583TAI-UTC offset (s) 584 585@item @code{leapsec} 586@tab 587NTP seconds when the next leap second is/was inserted 588 589@item @code{expire} 590@tab 591NTP seconds when the NIST leapseconds file expires 592 593@end multitable 594 595The jitter and wander statistics are exponentially-weighted RMS averages. 596The system jitter is defined in the NTPv4 specification; 597the clock jitter statistic is computed by the clock discipline module. 598 599When the NTPv4 daemon is compiled with the OpenSSL software library, 600additional system variables are displayed, including some or all of the 601following, depending on the particular Autokey dance: 602 603@multitable @columnfractions .1 .2 604@headitem Variable @tab Description 605 606@item @code{host} 607@tab 608Autokey host name for this host 609 610@item @code{ident} 611@tab 612Autokey group name for this host 613 614@item @code{flags} 615@tab 616host flags (see Autokey specification) 617 618@item @code{digest} 619@tab 620OpenSSL message digest algorithm 621 622@item @code{signature} 623@tab 624OpenSSL digest/signature scheme 625 626@item @code{update} 627@tab 628NTP seconds at last signature update 629 630@item @code{cert} 631@tab 632certificate subject, issuer and certificate flags 633 634@item @code{until} 635@tab 636NTP seconds when the certificate expires 637 638@end multitable 639 640@node Peer Variables, Clock Variables, System Variables, Top 641@comment node-name, next, previous, up 642@section Peer Variables 643 644The following peer variables appear in the @code{rv} billboard 645for each association. 646Not all variables are displayed in some configurations. 647 648@multitable @columnfractions .1 .2 649@headitem Variable @tab Description 650 651@item @code{associd} 652@tab 653association ID 654 655@item @code{status} 656@tab 657@url{decode.html#peer, peer status word} 658 659@item @code{srcadr} 660@itemx @code{srcport} 661@tab 662source (remote) IP address and port 663 664@item @code{dstadr} 665@itemx @code{dstport} 666@tab 667destination (local) IP address and port 668 669@item @code{leap} 670@tab 671leap indicator (0-3) 672 673@item @code{stratum} 674@tab 675stratum (0-15) 676 677@item @code{precision} 678@tab 679precision (log(2) s) 680 681@item @code{rootdelay} 682@tab 683total roundtrip delay to the primary reference clock 684 685@item @code{rootdisp} 686@tab total root dispersion to the primary reference clock 687 688@item @code{refid} 689@tab 690reference ID or @url{decode.html#kiss, kiss code} 691 692@item @code{reftime} 693@tab 694reference time 695 696@item @code{reach} 697@tab 698reach register (octal) 699 700@item @code{unreach} 701@tab 702unreach counter 703 704@item @code{hmode} 705@tab 706host mode (1-6) 707 708@item @code{pmode} 709@tab 710peer mode (1-5) 711 712@item @code{hpoll} 713@tab 714host poll exponent (log(2) s) (3-17) 715@item @code{ppoll} 716@tab 717peer poll exponent (log(2) s) (3-17) 718 719@item @code{headway} 720@tab 721headway (see @url{rate.html, Rate Management and the Kiss-o'-Death Packet}) 722 723@item @code{flash} 724@tab 725@url{decode.html#flash, flash status word} 726 727@item @code{offset} 728@tab 729filter offset 730 731@item @code{delay} 732@tab 733filter delay 734 735@item @code{dispersion} 736@tab 737filter dispersion 738 739@item @code{jitter} 740@tab 741filter jitter 742 743@item @code{ident} 744@tab 745Autokey group name for this association 746 747@item @code{bias} 748@tab 749unicast/broadcast bias 750 751@item @code{xleave} 752@tab 753interleave delay (see @url{xleave.html, NTP Interleaved Modes}) 754 755@end multitable 756 757The bias variable is calculated when the first broadcast packet is received 758after the calibration volley. It represents the offset of the broadcast 759subgraph relative to the unicast subgraph. The xleave variable appears 760only the interleaved symmetric and interleaved modes. It represents 761the internal queuing, buffering and transmission delays for the preceding 762packet. 763 764When the NTPv4 daemon is compiled with the OpenSSL software library, 765additional peer variables are displayed, including the following: 766 767@multitable @columnfractions .1 .2 768@headitem Variable @tab Description 769 770@item @code{flags} 771@tab 772peer flags (see Autokey specification) 773 774@item @code{host} 775@tab 776Autokey server name 777 778@item @code{flags} 779@tab 780peer flags (see Autokey specification) 781 782@item @code{signature} 783@tab 784OpenSSL digest/signature scheme 785 786@item @code{initsequence} 787@tab 788initial key ID 789 790@item @code{initkey} 791@tab 792initial key index 793 794@item @code{timestamp} 795@tab 796Autokey signature timestamp 797 798@end multitable 799 800@node Clock Variables, , Peer Variables, Top 801@comment node-name, next, previous, up 802@section Clock Variables 803 804The following clock variables appear in the @code{cv} billboard for each association with a reference clock. Not all variables are displayed in some configurations. 805 806@multitable @columnfractions .1 .2 807@headitem Variable @tab Description 808@item @code{associd} 809@tab association ID 810@item @code{status} 811@tab @url{decode.html#clock, clock status word} 812@item @code{device} 813@tab device description 814@item @code{timecode} 815@tab ASCII time code string (specific to device) 816@item @code{poll} 817@tab poll messages sent 818@item @code{noreply} 819@tab no reply 820@item @code{badformat} 821@tab bad format 822@item @code{baddata} 823@tab bad date or time 824@item @code{fudgetime1} 825@tab fudge time 1 826@item @code{fudgetime2} 827@tab fudge time 2 828@item @code{stratum} 829@tab driver stratum 830@item @code{refid} 831@tab driver reference ID 832@item @code{flags} 833@tab driver flags 834@end multitable 835