The description of the set statement asserts that the set must have been
created with the "dynamic" flag. However, this is not in fact the case,
and the assertion is contradicted by the following example, in which the
set is created with just the "timeout" flag (which suffices to ensure
that the kernel will create a set which can be updated). Remove the
assertion.
Signed-off-by: Jeremy Sowden <jeremy@xxxxxxxxxx>
---
doc/statements.txt | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/doc/statements.txt b/doc/statements.txt
index e17068a8a04b..847656ac7601 100644
--- a/doc/statements.txt
+++ b/doc/statements.txt
@@ -669,10 +669,9 @@ SET STATEMENT
~~~~~~~~~~~~~
The set statement is used to dynamically add or update elements in a set from
the packet path. The set setname must already exist in the given table and must
-have been created with the dynamic flag. Furthermore, these sets must specify
-both a maximum set size (to prevent memory exhaustion) and a timeout (so that
-number of entries in set will not grow indefinitely). The set statement can be
-used to e.g. create dynamic blacklists.
+specify both a maximum set size (to prevent memory exhaustion) and a timeout (so
+that number of entries in set will not grow indefinitely). The set statement can
+be used to e.g. create dynamic blacklists.
[verse]
{*add* | *update*} *@*'setname' *{* 'expression' [*timeout* 'timeout'] [*comment* 'string'] *}*
--
2.24.0
