<h2> => </h3>

[gosa.git] / gosa-core / contrib / gosa.conf.5

diff --git a/gosa-core/contrib/gosa.conf.5 b/gosa-core/contrib/gosa.conf.5
index 620dbdb86ef39de9b904ac2c9f41087f715f0e67..fac7b505394b9c3f2c849ce17159f68fdadfde69 100644 (file)
--- 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.
+.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.
+GOsa will not log anything, if the logging value is empty or set to
+false.
 .PP
 
 .B loginAttribute
@@ -1389,7 +1388,7 @@ GOsa/FAI methods.
 
 If you have only one release, or want to define a default release to be shown
 by GOsa, define the
-.I defaultFaiRelease
+.I defaultFaiRelease="ou=sarge,ou=fai,ou=configs,ou=syst..."
 within the 
 .I faiManagement
 class definition