Fixed Typo.

[gosa.git] / gosa-core / FAQ

diff --git a/gosa-core/FAQ b/gosa-core/FAQ
index 4d271ade21687dab0e25937a99ae722a9ba16032..41d4254ffb2795494fbeee21c30480b91bd49823 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,13 +398,3 @@ 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: The object listing is very slow when 'Search in subtrees' is active. 
-   Can I speed things up?
-
-A: There is a special handling for huge ldap servers, you can activate it by setting 
-   the sub_list_support to "true" in the location section of your gosa.conf.
-
-   <location name=...
-       sub_list_support="true"
-   ...>