]> git.ipfire.org Git - thirdparty/haproxy.git/commitdiff
DOC: config: removing "log-balance" references
authorAurelien DARRAGON <adarragon@haproxy.com>
Tue, 21 Nov 2023 10:28:26 +0000 (11:28 +0100)
committerWilly Tarreau <w@1wt.eu>
Fri, 24 Nov 2023 08:44:19 +0000 (09:44 +0100)
"log-balance" keyword was removed by b61147f ("MEDIUM: log/balance: merge
tcp/http algo with log ones") but it was still documented.

Removing "log-balance" references in the documentation where needed.

doc/configuration.txt

index 1f44785e8c1d4a489993c4828ff628c5a5d2a9ce..1fc9bca38f915f5929eeec22acdd2943ab613dc8 100644 (file)
@@ -4498,7 +4498,6 @@ id                                        -          X         X         X
 ignore-persist                            -          -         X         X
 load-server-state-from-file               X          -         X         X
 log                                  (*)  X          X         X         X
-log-balance                               X          -         X         X
 log-format                                X          X         X         -
 log-format-sd                             X          X         X         -
 log-tag                                   X          X         X         X
@@ -9114,10 +9113,9 @@ mode { tcp|http|log }
               any "log" directive by using the "backend@<name>" syntax. Log
               messages will be distributed to the servers from the backend
               according to the lb settings which can be configured using the
-              "log-balance" keyword (in place of the "balance" keyword for TCP
-              and HTTP backends). Log backends support UDP servers by prefixing
+              "balance" keyword. Log backends support UDP servers by prefixing
               the server's address with the "udp@" prefix. Common backend and
-              server features are supported, but not TCP or HTTP related ones.
+              server features are supported, but not TCP or HTTP specific ones.
 
   When doing content switching, it is mandatory that the frontend and the
   backend are in the same mode (generally HTTP), otherwise the configuration