summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 87c1662)
raw | patch | inline | side by side (parent: 87c1662)
author | hickert <hickert@594d385d-05f5-0310-b6e9-bd551577e9d8> | |
Mon, 9 Jun 2008 12:01:23 +0000 (12:01 +0000) | ||
committer | hickert <hickert@594d385d-05f5-0310-b6e9-bd551577e9d8> | |
Mon, 9 Jun 2008 12:01:23 +0000 (12:01 +0000) |
git-svn-id: https://oss.gonicus.de/repositories/gosa/trunk@11267 594d385d-05f5-0310-b6e9-bd551577e9d8
gosa-core/FAQ | patch | blob | history |
diff --git a/gosa-core/FAQ b/gosa-core/FAQ
index 41d4254ffb2795494fbeee21c30480b91bd49823..cd802eb39fe22483c04fd2cc208297dcbdbcbc39 100644 (file)
--- a/gosa-core/FAQ
+++ b/gosa-core/FAQ
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>
+
+
+
+
+