-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 2 Nov 2002, Andrew Bartlett wrote:
> If we are a normally bound to an ldap slave, and use and ldap referral > to contact the master, we encounter the problem that the slave hasn't > caught up by the time we do the next search on the slave. This is part of LDAP. Loose replication. > Aside from restructuring Samba to add some form of cache (which I really > would prefer to avoid), is there any way to get some form of sequence > number that we can poll a slave for, that would indicate that it is 'up > to date'? What are you looking for. > I was thinking that we could get such a value in the return from the ADD > operation, and poll the slave until it catches up. Why not just remember the server you contacted. This is what we had to do with a buggy Windows NT 4.0 domain before when adding a ourselves as a domain member. Bind to the PDC (not ldap of course, but basic idea is the same). > Does anything like this exist? Are there any moves to add a global > sequence number (which we need for Active Directory stuff in the longer > term anyway), or some other cookie that we can use for 'up to date' > checks? Not that I am aware of. You could try to implement one, but i don't think you are guaranteed and order of change replication so the new "up-to-date" id could be replicated before the other information in theory. Probably not true in practice with OpenLDAP, but possibly given a thread slapd writing out to a change log. cheers, jerry --------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc ISBN 0-672-32269-2 "SAMS Teach Yourself Samba in 24 Hours" 2ed "I never saved anything for the swim back." Ethan Hawk in Gattaca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE9yhnNIR7qMdg1EfYRAnCBAJ9yGW0L4QHkk8NKNKFiouuThiNyLwCfRjum DSYWqTdq1eLRds6e7TX3Re0= =NV4l -----END PGP SIGNATURE-----
