From 1857b8cf4dc526fc6a11e6f83b0dc95f90ca269a Mon Sep 17 00:00:00 2001 From: Matteo Contrini Date: Fri, 16 Oct 2020 17:35:54 +0200 Subject: [PATCH] DOC: fix typo in MAX_SESS_STKCTR MAX_SESS_STKCTR is spelled wrongly a couple of times in the configuration docs (K and C are swapped). This patch fixes the typos. --- doc/configuration.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 678d2ee26..a32f6968a 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -6095,7 +6095,7 @@ http-request track-sc2 [table ] [ { if | unless } ] not stop evaluation and do not change default action. The number of counters that may be simultaneously tracked by the same connection is set in MAX_SESS_STKCTR at build time (reported in haproxy -vv) which defaults to 3, - so the track-sc number is between 0 and (MAX_SESS_STCKTR-1). The first + so the track-sc number is between 0 and (MAX_SESS_STKCTR-1). The first "track-sc0" rule executed enables tracking of the counters of the specified table as the first set. The first "track-sc1" rule executed enables tracking of the counters of the specified table as the second set. The first @@ -11092,7 +11092,7 @@ tcp-request connection [{if | unless} ] number of counters that may be simultaneously tracked by the same connection is set in MAX_SESS_STKCTR at build time (reported in haproxy -vv) which defaults to 3, so the track-sc number is between 0 - and (MAX_SESS_STCKTR-1). The first "track-sc0" rule executed enables + and (MAX_SESS_STKCTR-1). The first "track-sc0" rule executed enables tracking of the counters of the specified table as the first set. The first "track-sc1" rule executed enables tracking of the counters of the specified table as the second set. The first "track-sc2" rule executed