From f3693ad46ec3fcac10f74384e0c842a087c1e751 Mon Sep 17 00:00:00 2001 From: Pierangelo Masarati Date: Tue, 3 Jul 2007 09:45:28 +0000 Subject: [PATCH] import fix for default loglevel (ITS#5027) --- CHANGES | 2 ++ doc/man/man5/slapd.conf.5 | 3 ++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/CHANGES b/CHANGES index 93a735b8fd..938c23f9cf 100644 --- a/CHANGES +++ b/CHANGES @@ -2,6 +2,8 @@ OpenLDAP 2.3 Change Log OpenLDAP 2.3.37 Engineering Clarified slapd-perl SampleLDAP.pm usage (ITS#4995) + Documentation + Fixed slapd.conf(5) for default loglevel (ITS#5027) OpenLDAP 2.3.36 Release (2007/06/17) Fixed slapd error code on Windows (ITS#4945, #4606) diff --git a/doc/man/man5/slapd.conf.5 b/doc/man/man5/slapd.conf.5 index 7ed7c2c0ba..88b840857d 100644 --- a/doc/man/man5/slapd.conf.5 +++ b/doc/man/man5/slapd.conf.5 @@ -607,10 +607,11 @@ The keyword .BR none , or the equivalent integer representation, causes those messages that are logged regardless of the configured loglevel to be logged. -In fact, if no loglevel (or a 0 level) is defined, no logging occurs, +In fact, if loglevel is set to 0, no logging occurs, so at least the .B none level is required to have high priority messages logged. +The loglevel defaults to \fBstats\fP. .RE .TP .B moduleload -- 2.47.2