summaryrefslogtreecommitdiff
path: root/source3/libads
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
commit2001b83faa9f0438adda40ffe12fea4a3dc6a733 (patch)
tree86e2df96bafa6267a406bbffc340fa329ac30095 /source3/libads
parent9802310b2aa919964f4f312cd99349d02cc12afc (diff)
downloadsamba-2001b83faa9f0438adda40ffe12fea4a3dc6a733.tar.gz
samba-2001b83faa9f0438adda40ffe12fea4a3dc6a733.tar.bz2
samba-2001b83faa9f0438adda40ffe12fea4a3dc6a733.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! (This used to be commit 93389647203395da0e894c2e57348081e755884a)
Diffstat (limited to 'source3/libads')
-rw-r--r--source3/libads/ldap.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/source3/libads/ldap.c b/source3/libads/ldap.c
index aa6e7c0036..e53f6d87db 100644
--- a/source3/libads/ldap.c
+++ b/source3/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);
}
/*