Re: Corrupt LDAP DB ... ans 2.3.11 syncrepl

[Leigh Porter <leighldap@leighporter.org>]

Hiya all,

I tried refreshAndPersist and replication died - did I do something stoopid?


syncrepl rid=123
       provider=ldap://10.100.100.30:389
       type=refreshOnly
       interval=00:00:00:20
       searchbase="dc=ukbboss,dc=co,dc=uk"
       filter="(objectClass=qmailUser)"
       scope=sub                     
attrs="sn,cn,mailDomain,mailUsername,mail,mailMessageStore,qmailUID,mailServices,accountStatus,mailQuotaSize,userPassword,Tier-Of-service,Roaming-Indication,PrimaryUser,Additional-PDP-Contexts-Allowed,User-Trace-Indicator"
       schemachecking=off
       bindmethod=simple
       binddn="cn=Manager,dc=ukbboss,dc=co,dc=uk"
       credentials=cheese


#type=refreshAndPersist
#

Buchan Milne wrote:

> On Friday 28 October 2005 15:10, leighldap wrote:
>
>
>  
>
> > I currently syncrepl every 20 seconds, is this OK or will it break?
> > Whap happens is a syncrepl takes longer than 20 seconds
> > to complete, will it block the next syncrepl until it completes?
> >    
>
> Use refreshAndPersist and it will get the changes immediately on its own.
>
> Regards,
> Buchan
>
>