From: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: [nft PATCH 3/4] doc: document export op
Date: Wed, 14 May 2014 17:36:22 +0200 [thread overview]
Message-ID: <20140514153622.25186.9873.stgit@nfdev.cica.es> (raw)
In-Reply-To: <20140514153146.25186.58208.stgit@nfdev.cica.es>
Let's document the `nft export [xml|json]' command.
Signed-off-by: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
---
doc/nft.xml | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/doc/nft.xml b/doc/nft.xml
index 1de4b3f..61ca03a 100644
--- a/doc/nft.xml
+++ b/doc/nft.xml
@@ -2080,6 +2080,28 @@ filter input iif eth0 drop
</refsect1>
<refsect1>
+ <title>Additional commands</title>
+ <para>
+ These are some additional commands included in nft.
+ </para>
+ <refsect2>
+ <title>export</title>
+ <para>
+ Export your current ruleset in XML or JSON format to stdout.
+ </para>
+ <para>
+ Examples:
+ <programlisting>
+% nft export xml
+[...]
+% nft export json
+[...]
+ </programlisting>
+ </para>
+ </refsect2>
+ </refsect1>
+
+ <refsect1>
<title>Error reporting</title>
<para>
When an error is detected, nft shows the line(s) containing the error, the position
next prev parent reply other threads:[~2014-05-14 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 15:36 [nft PATCH 0/4] small updates to documentation Arturo Borrero Gonzalez
2014-05-14 15:36 ` [nft PATCH 1/4] doc: fix indendation of examples Arturo Borrero Gonzalez
2014-05-14 15:36 ` [nft PATCH 2/4] doc: update return code for NFT_EXIT_NONL Arturo Borrero Gonzalez
2014-05-14 15:36 ` Arturo Borrero Gonzalez [this message]
2014-05-14 15:36 ` [nft PATCH 4/4] doc: document monitor op Arturo Borrero Gonzalez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140514153622.25186.9873.stgit@nfdev.cica.es \
--to=arturo.borrero.glez@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).