Hi,
I noticed that MAX_SESS_STKCTR is spelled wrong twice in the docs, so here's a
patch to fix it.
I hope I didn't get anything wrong since it's my first contribution here. Also,
I'm not subscribed to the list so if you could CC me in replies it would be
appreciated.
Thanks!
--
Matteo
>From be7ae1db8d9ba8349b56a2f539a6d2a13dbfc6ef Mon Sep 17 00:00:00 2001
From: Matteo Contrini <mat...@contrini.it>
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 6a90bfadb..4bc917929 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -6095,7 +6095,7 @@ http-request track-sc2 <key> [table <table>] [ { if |
unless } <condition> ]
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
@@ -11091,7 +11091,7 @@ tcp-request connection <action> [{if | unless}
<condition>]
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
--
2.28.0.windows.1
