summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndrew Tridgell <tridge@samba.org>2002-03-13 06:43:52 +0000
committerAndrew Tridgell <tridge@samba.org>2002-03-13 06:43:52 +0000
commit93389647203395da0e894c2e57348081e755884a (patch)
treea61571eb12250418d614052ad7fa1d6687e7f950
parentf81882fc9510aadd7d1db77753b307800ab50f9b (diff)
downloadsamba-93389647203395da0e894c2e57348081e755884a.tar.gz
samba-93389647203395da0e894c2e57348081e755884a.tar.xz
samba-93389647203395da0e894c2e57348081e755884a.zip
detect SIZELIMIT_EXCEEDED in ldap queries and truncate
the problem is, how the heck do we properly handle these? Jerry? It seems that the Win2000 ADS server only returns a max of 1000 records!
-rw-r--r--source/libads/ldap.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/source/libads/ldap.c b/source/libads/ldap.c
index aa6e7c00369..e53f6d87db3 100644
--- a/source/libads/ldap.c
+++ b/source/libads/ldap.c
@@ -84,6 +84,10 @@ ADS_STATUS ads_do_search(ADS_STRUCT *ads, const char *bind_path, int scope,
bind_path, scope,
exp, (char **) attrs, 0, NULL, NULL,
&timeout, LDAP_NO_LIMIT, (LDAPMessage **)res);
+ if (rc == LDAP_SIZELIMIT_EXCEEDED) {
+ DEBUG(3,("Warning! sizelimit exceeded in ldap. Truncating.\n"));
+ rc = 0;
+ }
return ADS_ERROR(rc);
}
/*