2013/4/26 Marc Patermann hans.moser@ofd-z.niedersachsen.de:
Meike Stone schrieb (26.04.2013 14:34 Uhr):
Is it possible to simulate the present phase with ldapsearch, to look if the provider needs so long and if, what part (entries updated or unchanged entry ) needs so long?
look at # man ldapsearch for "-E" and sync=rp[/<cookie>][/<slimit>] "(LDAP Sync refreshAndPersist)" cookie is something like "rid=${RID},csn=${CSN}
But I'm not sure, it does what you want.
For that point yes, thanks.
I tried it: - got the ContextCSN on server via ldapsearch -x -h localhost -w password -D cn=admin,ou=root -bou=root -s base contextCSN -LLL - waited for about 20min - startet a refreshOnly ldapsearch -x -h localhost -wpassword -D"cn=admin,ou=root" -b"ou=root" -s sub -E sync=ro/rid=103,csn=20130426125054.388178Z#000000#001#000000/0 and got the whole directory back.
I thought, only modified entries are transmitted completely and unmodified entires are empty (plus entryUUID) is sent?
Is this check valid? If I use slapd, get the contextCSN, do nothing modify, and start the ldapsearch -E ..., I should only get back empty entires plus entryUUID? I'm wrong?
Thanks Meike