Finalized set properties

[gosa.git] / gosa-core / FAQ

diff --git a/gosa-core/FAQ b/gosa-core/FAQ
index c0e46ea49eecd8f9700e8dd614fd15d1928652e3..b93049df6e42d02f32ee41b4922db8785b978263 100644 (file)
--- a/gosa-core/FAQ
+++ b/gosa-core/FAQ
@@ -332,14 +332,6 @@ A: For Kolab to work correctly you have to include the rfc2739.schema
    in your slapd.conf. Insert it before the kolab2.schema
 
 
-Q: Is there a way to let GOsa automatically fill missing fields in the network
-   configuration?
-
-A: Sure. You can specify the "auto_network_hook" 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?
 
@@ -406,3 +398,27 @@ Q: GOsa only shows 300 entries at a time. Is this normal?
 
 A: There's a default sizelimit. You can set the "sizelimit" option in your
    gosa.conf's  location section to a higher value to get rid of it.
+
+
+Q: I have problems with my ldap server when I open groups with 
+   a huge amount of members, what can I do?
+
+A: You can set a nesting limit which ensures that the user names will not be 
+   resolved if the amount of members reaches this limit.
+   <location
+        LDAP_FILTER_NESTING_LIMIT="100"
+   </location>
+
+
+Q: I want to disable the "Is the configuration file up to date?" check when logging in.
+   How can I disable this check?
+
+A: Just set the config_version attribute to an empty value:
+   <conf config_version="" >
+
+ 
+
+
+       
+
+