[Git][NTPsec/ntpsec][master] Fix more ntpq man page formatting

Richard Laager (@rlaager) gitlab at mg.gitlab.com
Fri Oct 29 23:57:25 UTC 2021



Richard Laager pushed to branch master at NTPsec / ntpsec


Commits:
db531373 by Richard Laager at 2021-10-29T18:50:04-05:00
Fix more ntpq man page formatting

The previous fix only fixed this in asciidoc, not asciidoctor.
Also, there were other examples of the same type of text that either
needed fixing or were not formatted consistently.

Signed-off-by: Richard Laager <rlaager at wiktel.com>

- - - - -


1 changed file:

- docs/includes/ntpq-body.adoc


Changes:

=====================================
docs/includes/ntpq-body.adoc
=====================================
@@ -307,7 +307,7 @@ ind assid status conf reach auth condition last_event cnt
   server so loaded that none of its MRU entries age out before they
   are shipped. With this option, each segment is reported as it arrives.
 
-[[mrulist]]+mrulist+ [+limited+ | +kod+ | +mincount=+'count' | +mindrop=+'drop' | +minscore=+'score' | +maxlstint=+'seconds' | +minlstint=+'seconds' | +laddr=+'localaddr' | +sort=+'sortorder' | +resany=+'hexmask' | +resall=+'hexmask' | +limit=+'limit' | +addr.'num'=+'address']::
+[[mrulist]]+mrulist+ [+limited+ | +kod+ | +mincount=+'count' | +mindrop=+'drop' | +minscore=+'score' | +maxlstint=+'seconds' | +minlstint=+'seconds' | +laddr=+'localaddr' | +sort=+'sortorder' | +resany=+'hexmask' | +resall=+'hexmask' | +limit=+'limit' | +addr.+'num'+=+'address']::
   Obtain and print traffic counts collected and maintained by the
   monitor facility. This is useful for tracking who _uses_ or
   _abuses_ your server.
@@ -316,19 +316,19 @@ Except for +sort=+'sortorder', the options
 filter the list returned by +ntpd+. The +limited+ and +kod+ options
 return only entries representing client addresses from which the last
 packet received triggered either discarding or a KoD response.
-the +addr.'num'=+ option adds specific addresses to retrieve when
+the +addr.+'num'+=+ option adds specific addresses to retrieve when
 +limit=+'1'. Values of 0 to 15 are supported for 'num'. Also, used
-internally with +last.'num'=+'hextime' to select the starting point
+internally with +last.+'num'+=+'hextime' to select the starting point
 for retrieving continued response.
 the +frags=+'frags' option limits the number of datagrams
 (fragments) in response.  Used by newer ntpq versions instead
 of limit= when retrieving multiple entries.
 The +limit=+ option limits the MRU entries returned per response.
 limit=1 is a special case:  Instead of fetching beginning with
-the supplied starting points (provided by a last.x and addr.x
+the supplied starting points (provided by a last.'x' and addr.'x'
 where 0 <= x <= 15, default the beginning of time) newer neighbor,
 fetch the supplied entries. This enables fetching multiple entries
-from given IP addresses (provided by addr.x= entries where 0 <= x
+from given IP addresses (provided by addr.'x'= entries where 0 <= x
 <= 15). When limit is not one and frags= is provided,
 the fragment limit controls. NOTE: a single mrulist command may
 cause many query/response rounds allowing limits as low as 3 to



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/-/commit/db531373e81c68198ca6170f1e54ea966c0ce2ab

-- 
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/-/commit/db531373e81c68198ca6170f1e54ea966c0ce2ab
You're receiving this email because of your account on gitlab.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20211029/bec79dbe/attachment-0001.htm>


More information about the vc mailing list