import fix for default loglevel (ITS#5027)

diff --git a/CHANGES b/CHANGES
index 93a735b8fdbcb406b16b6d2c12debeba4c7c961e..938c23f9cf043d5fab279f7afbc1ee2975265262 100644 (file)
--- 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 7ed7c2c0ba2d3ace6027c159234b98f344e4b993..88b840857df2d69927b95886a9250c80ad627541 100644 (file)
--- 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 <filename>