Here is the primary database definition, and it's the tree that I'm trying to run a persistent search against. I have the syncprov overlay loaded towards the end after the syncrepl and accesslog stuff. The "overlay syncprov" three lines are the only lines in slapd.conf that reference syncprov. Thanks! Tom
database bdb suffix "dc=coas,dc=oregonstate,dc=edu" rootdn "XXX" rootpw secret directory /usr/local/var/openldap-data index objectClass eq index ou,cn,mail,surname,givenname eq,pres,sub index uid,memberUid eq,pres,sub index uniqueMember eq,pres index entryCSN,entryUUID eq
syncrepl rid=123 provider=ldap://XXX starttls=critical type=refreshAndPersist interval=00:00:05:00 retry="5 20 300 +" searchbase="dc=coas,dc=oregonstate,dc=edu" filter="(objectClass=*)" attrs="*,+" scope=sub schemachecking=off bindmethod=simple binddn="XXX" credentials=XXX
mirrormode TRUE
overlay accesslog logdb cn=accesslog logops add delete modify modrdn logold (objectclass=person) logsuccess TRUE logpurge 07+00:00 01+00:00
overlay syncprov syncprov-checkpoint 100 10 syncprov-sessionlog 100
On 08/24/2010 05:39 PM, Quanah Gibson-Mount wrote:
--On Tuesday, August 24, 2010 5:26 PM -0700 Tom Leach leach@coas.oregonstate.edu wrote:
I'm under the impression that PersistentSearch is enabled by the syncprov overlay so why would I be getting the unknown control message?
Did you load and enable the overlay for your primary database?
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration