diff options
| author | Jan Engelhardt <jengelh@inai.de> | 2023-10-24 14:58:06 +0200 |
|---|---|---|
| committer | Phil Sutter <phil@nwl.cc> | 2023-10-27 18:00:30 +0200 |
| commit | b7d45c140fde9366a34412dbd318dd7c84bbef14 (patch) | |
| tree | 45e43ef8d3fb0503d221a90e4f6bdcac17e53071 /extensions/libxt_hashlimit.man | |
| parent | 458e167e9510f995111d32aa7a30b7c7d2af2e75 (diff) | |
man: encode minushyphen the way groff/man requires it
Sparked by a recent LWN article[1], sweeps over the iptables manpages
for incorrectly encoded dashes was made by Phil Sutter and myself.
An ASCII minushyphen in the source manpage translates to a hyphen in
output, so one has to use the sequence "\-" to get a minushyphen in
the output, as groff_char(7) explains.
[1] https://lwn.net/Articles/947941/ (paywalled until about 2023-11-06)
Signed-off-by: Jan Engelhardt <jengelh@inai.de>
Signed-off-by: Phil Sutter <phil@nwl.cc>
Diffstat (limited to 'extensions/libxt_hashlimit.man')
| -rw-r--r-- | extensions/libxt_hashlimit.man | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/extensions/libxt_hashlimit.man b/extensions/libxt_hashlimit.man index 8a35d564..627fcd0a 100644 --- a/extensions/libxt_hashlimit.man +++ b/extensions/libxt_hashlimit.man @@ -77,8 +77,8 @@ in 10.0.0.0/8" => .TP matching bytes per second "flows exceeding 512kbyte/s" => -\-\-hashlimit-mode srcip,dstip,srcport,dstport \-\-hashlimit\-above 512kb/s +\-\-hashlimit\-mode srcip,dstip,srcport,dstport \-\-hashlimit\-above 512kb/s .TP matching bytes per second "hosts that exceed 512kbyte/s, but permit up to 1Megabytes without matching" -\-\-hashlimit-mode dstip \-\-hashlimit\-above 512kb/s \-\-hashlimit-burst 1mb +\-\-hashlimit\-mode dstip \-\-hashlimit\-above 512kb/s \-\-hashlimit\-burst 1mb |