summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorIsmo Puustinen <ismo.puustinen@intel.com>2017-06-28 11:16:57 +0300
committerPablo Neira Ayuso <pablo@netfilter.org>2017-06-28 17:35:50 +0200
commit27e4cf73880b7103bffb747cdce8f9eb10e03b39 (patch)
tree77479ff486f70beabc2ba84e0fd860d8429b0dd3
parent03a17f80bab09f8d9585b70464634ca50d3ffc7c (diff)
man: add include statement documentation.
Add to man page information about using the wildcard include statements. Signed-off-by: Ismo Puustinen <ismo.puustinen@intel.com> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
-rw-r--r--doc/nft.xml9
1 files changed, 7 insertions, 2 deletions
diff --git a/doc/nft.xml b/doc/nft.xml
index 970acb54..9c9192cf 100644
--- a/doc/nft.xml
+++ b/doc/nft.xml
@@ -229,8 +229,13 @@ vi:ts=4 sw=4
-h/--help option.
</para>
<para>
- If the <literal>filename</literal> parameter is a directory, then all files in
- the directory are loaded in alphabetical order.
+ Include statements support the usual shell wildcard symbols
+ (<literal>*,?,[]</literal>). Having no matches for an include statement is not
+ an error, if wildcard symbols are used in the include statement. This allows having
+ potentially empty include directories for statements like
+ <literal>include "/etc/firewall/rules/*"</literal>. The wildcard matches are
+ loaded in alphabetical order. Files beginning with dot (<literal>.</literal>) are
+ not matched by include statements.
</para>
</refsect2>
<refsect2>