[Date Prev][Date Next] [Chronological] [Thread] [Top]

Wired issue with slurpd


I am using slurpd to do replication (openldap 2.3.33) and encountered a strange issue:

The master have an entry which has a binary field, size of filed is about 10 meg. When never this field is updated ( and it's the only field get updated), slurpd is triggered to replicate the change to the slave. But slurpd seems gone wild on this binary filed, when i check the replication log, i saw this binary filed becomes huge, i mean really huge, gigabytes in size.

Is there any problem with slurpd to read the binary filed?