From 5b3a3136ad8835842a7913412b9de1db0284a15f Mon Sep 17 00:00:00 2001
From: Jan Kadlec <jan.kadlec@nic.cz>
Date: Fri, 17 Aug 2012 15:27:15 +0200
Subject: [PATCH] Clarification to logging section of conf. reference
---
doc/reference.texi | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/doc/reference.texi b/doc/reference.texi
index 124da1205d..9baec29b82 100644
--- a/doc/reference.texi
+++ b/doc/reference.texi
@@ -687,9 +687,11 @@ loaded even upon discovering an error:
The @code{log} statement configures logging output of Knot DNS. You
can configure Knot DNS to log into file or system log. There are several
logging categories to choose from. Each log
-message has its priority and you can configure priorities for each
+message has its severity and user can configure severities for each
log destination.
+In case of missing log section, @emph{errors} from all categories will be logged to @emph{stderr} and to @emph{syslog}. No other severities shall be logged!
+
@node log_name
@subsubsection @kbd{log_name}
@vindex @kbd{log_name}
@@ -728,6 +730,8 @@ Knot DNS has the following logging severities:
@item @emph{all} - All severities.
@end itemize
+More severites may be listed for each category, but all severities have to be listed explicitely, i.e. using @emph{error} severity does not mean that @emph{warning} severity messages will be logged as well.
+
@node log_file
@subsubsection @kbd{log_file}
@vindex @kbd{log_file}
--
GitLab