Updated spec file

[gosa.git] / FAQ

diff --git a/FAQ b/FAQ
index b797424d3bcd2cf7114dc5763a50047c21181fc6..697f75363bff36f53953ed77e49bfb74fd3a4650 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -312,22 +312,6 @@ Q: How can i active the account expiration code for the gosa interface?
 
 A: Yes. Just set "account_expiration" to "true" in your gosa.conf's main section.
 
-Q: How can i activate the object snapshot functionality?
-
-A: Add these lines in the main section of your gosa.conf
-   enable_snapshot     ="true"
-   snapshot_base       ="ou=snapshots,dc=server,dc=de"
-
-
-Q: How can i store object snapshots on another server?
-
-A: Just add these lines in the main section of your gosa conf
-
-   snapshot_ldap_base  ="dc=server,dc=de"
-   snapshot_user       ="cn=ldapadmin,dc=server,dc=de"
-   snapshot_password   ="password"
-   snapshot_server     ="ldap://server:389"
-
 
 Q: What is the correct connection string for a Kolab server in GOsa?
 
@@ -351,6 +335,13 @@ A: For Kolab to work correctly you have to include the rfc2739.schema
 Q: Is there a way to let GOsa automatically fill missing fields in the network
    configuration?
 
-A: Sure. You can specify the "autoconf" option and provide the contributed
+A: Sure. You can specify the "auto_network_conf" option and provide the contributed
    script "net-resolver.sh" in your gosa.conf. If this is configured, you're
    getting an additional button in each network dialog.
+
+
+Q: New implementations of OpenLDAP seem to require {sasl} instead of {kerberos}
+   in password hashes. GOsa writes the wrong string. What can I do?
+
+A: You can set "krbsasl" to "true" in your gosa.conf's main section.
+