From: Jan Engelhardt <jengelh@inai.de>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH 8/9] doc: name the supported log levels for ipt_LOG
Date: Wed, 10 Oct 2012 14:26:31 +0200 [thread overview]
Message-ID: <1349871992-31115-9-git-send-email-jengelh@inai.de> (raw)
In-Reply-To: <1349871992-31115-1-git-send-email-jengelh@inai.de>
Leonardo Ferreira da Silva Boiko lets it be known that syslogd.conf may
not exist on certain systems. Referencing that manpage is not a good
idea in any case, I believe, since the strings that are accepted are
defined by iptables and not a syslog implementation.
References: http://bugs.debian.org/567564
Signed-off-by: Jan Engelhardt <jengelh@inai.de>
---
extensions/libip6t_LOG.man | 5 ++++-
extensions/libipt_LOG.man | 5 ++++-
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/extensions/libip6t_LOG.man b/extensions/libip6t_LOG.man
index b7803fe..0a48640 100644
--- a/extensions/libip6t_LOG.man
+++ b/extensions/libip6t_LOG.man
@@ -11,7 +11,10 @@ separate rules with the same matching criteria, first using target LOG
then DROP (or REJECT).
.TP
\fB\-\-log\-level\fP \fIlevel\fP
-Level of logging (numeric or see \fIsyslog.conf\fP(5)).
+Level of logging, which can be (system-specific) numeric or a mnemonic.
+Possible values are (in decreasing order of priority): \fBemerg\fP,
+\fBalert\fP, \fBcrit\fP, \fBerror\fP, \fBwarning\fP, \fBnotice\fP, \fBinfo\fP
+or \fBdebug\fP.
.TP
\fB\-\-log\-prefix\fP \fIprefix\fP
Prefix log messages with the specified prefix; up to 29 letters long,
diff --git a/extensions/libipt_LOG.man b/extensions/libipt_LOG.man
index 47c35e0..f2574f8 100644
--- a/extensions/libipt_LOG.man
+++ b/extensions/libipt_LOG.man
@@ -11,7 +11,10 @@ separate rules with the same matching criteria, first using target LOG
then DROP (or REJECT).
.TP
\fB\-\-log\-level\fP \fIlevel\fP
-Level of logging (numeric or see \fIsyslog.conf\fP(5)).
+Level of logging, which can be (system-specific) numeric or a mnemonic.
+Possible values are (in decreasing order of priority): \fBemerg\fP,
+\fBalert\fP, \fBcrit\fP, \fBerror\fP, \fBwarning\fP, \fBnotice\fP, \fBinfo\fP
+or \fBdebug\fP.
.TP
\fB\-\-log\-prefix\fP \fIprefix\fP
Prefix log messages with the specified prefix; up to 29 letters long,
--
1.7.10.4
next prev parent reply other threads:[~2012-10-10 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 12:26 Documentation fixes to iptables Jan Engelhardt
2012-10-10 12:26 ` [PATCH 1/9] doc: rename .8.in files to .8in Jan Engelhardt
2012-10-10 16:20 ` Pablo Neira Ayuso
2012-10-10 12:26 ` [PATCH 2/9] doc: add package version to all manpages Jan Engelhardt
2012-10-10 12:26 ` [PATCH 3/9] doc: fixup omissions in ip6tables-restore.8 Jan Engelhardt
2012-10-10 16:21 ` Pablo Neira Ayuso
2012-10-10 12:26 ` [PATCH 4/9] doc: document iptables-restore's -t option Jan Engelhardt
2012-10-10 12:26 ` [PATCH 5/9] doc: document iptables-restore's -v option Jan Engelhardt
2012-10-10 12:26 ` [PATCH 6/9] doc: document iptables-restore's -M option Jan Engelhardt
2012-10-10 12:26 ` [PATCH 7/9] doc: document iptables-restore's -h option Jan Engelhardt
2012-10-10 12:26 ` Jan Engelhardt [this message]
2012-10-10 12:26 ` [PATCH 9/9] src: remove faulty deprecated marker in libipt_LOG source Jan Engelhardt
2012-10-10 12:38 ` Documentation fixes to iptables Pablo Neira Ayuso
2012-10-10 13:04 ` Jan Engelhardt
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=1349871992-31115-9-git-send-email-jengelh@inai.de \
--to=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).