From: cajus <cajus@594d385d-05f5-0310-b6e9-bd551577e9d8>
Date: Tue, 29 Dec 2009 11:59:18 +0000 (+0000)
Subject: Updated manpage
X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=137303c0bee55077a9a375a65f11e129836e6d06;p=gosa.git

Updated manpage


git-svn-id: https://oss.gonicus.de/repositories/gosa/trunk@14977 594d385d-05f5-0310-b6e9-bd551577e9d8
---

diff --git a/gosa-core/contrib/gosa.conf.5 b/gosa-core/contrib/gosa.conf.5
index 620dbdb86..88e4b8b6d 100644
--- a/gosa-core/contrib/gosa.conf.5
+++ b/gosa-core/contrib/gosa.conf.5
@@ -241,14 +241,13 @@ for Sun DS based systems.
 The
 .I logging
 statement enables event logging on GOsa side. Setting it to 
-.I syslog,
-GOsa will log every action a user performs via syslog. Setting it to
-.I mysql,
-GOsa will log every action to a mysql server, defined in the
-GOsa systems plugin. Both values can be combined as a comma seperated
-list.
-
-GOsa will not log anything, if the logging value is empty.
+.I true,
+GOsa will log every action a user performs via syslog. If you use
+rsyslog and configure it to mysql logging, you can browse all events
+within GOsa.
+
+GOsa will not log anything, if the logging value is empty or set to
+false.
 .PP
 
 .B loginAttribute