Michael, yes, I read you answer. I missed the 'latter' and thought that you meant the persistentSearch was supplied by syncprov and not syncrepl. I guess I read latter but was thinking former.
I also read Dieter's answer pointing to SyncRequest but here's my issue. He states that the module (according to the author) needs refreshOnly and won't connect with refreshAndPersist. I need refreshAndPersist to make sure that my multi-master work correctly and a change on either server is quickly replicated to the other.
I've also read both the RFC and the (expired) draft for persistentSearch. It appears that persistentSearch has died and there is no server-side push type replacement. That's unfortunate since I will now need to poll on a frequent basis to catch a change that happens on a very infrequent basis.
Anyway, it looks like PersistentSearch isn't supported. Other approaches that I'm investigating are the accesslog with a process that queries it on a reqular basis looking for modifies, or create another syncrepl instance with a refreshOnly aimed at my client process.
Thanks! Tom
On 08/26/2010 01:09 AM, Michael Ströder wrote:
Tom Leach wrote:
Dieter, what I'm trying to do is have a separate process (this being the perl script) connect with a persistent search to one of a pair of syncrepl'd multimasters. Are syncrepl and syncprov mutually exclusive? If that's the case, then I'll have to take another tack since I require the syncrepl multimasters and the persistent search via syncprov was a "nice thing to have" but not required.
Tom,
did you really read my answer? http://www.openldap.org/lists/openldap-technical/201008/msg00226.html
Did you read Dieter's answer? Dieter even pointed you to Net::LDAP::Control::SyncRequest.
It's the client-side programming.
Ciao, Michael.