DOC: configuration: explicit multi-choice on bind shards option
authorBasha Mougamadou <b.mougamadou@criteo.com>
Wed, 14 May 2025 15:50:47 +0000 (15:50 +0000)
committerWilly Tarreau <w@1wt.eu>
Tue, 20 May 2025 14:44:14 +0000 (16:44 +0200)
From the documentation, this wasn't clear enough that shards should
be followed by one of the options number / by-thread / by-group.
Align it with existing options in documentation so that it becomes
more explicit.

(cherry picked from commit 824bb93e18043876a0fa30eeb3de50ea0ccb4ea5)
Signed-off-by: Willy Tarreau <w@1wt.eu>

doc/configuration.txt

index 848f45c..23b0c2d 100644 (file)
@@ -17337,7 +17337,7 @@ severity-output <format>
   - "string" severity level is prepended as a string following the
     rfc5424 convention.
 
-shards <number> | by-thread | by-group
+shards { <number> | by-thread | by-group }
   In multi-threaded mode, on operating systems supporting multiple listeners on
   the same IP:port, this will automatically create this number of multiple
   identical listeners for the same line, all bound to a fair share of the number