It used to be that if I ran "tail -f slurpd.replog," I would see a message like "slurpd.replog: file truncated" after slurpd updated the replicas. Now the file just grows and grows. It's almost as if the latest version of slurpd just doesn't clean up after itself.
-- Jacob Elder
Quoting matthew sporleder <msporleder@gmail.com>:
There's a that from slapd that's consumed and a log from slurdthat's
growinga log of what it's done.
On 1/27/06, Jacob Elder <jake@trec.us> wrote:We are running slapd 2.2.26-5 on Debian. We have a master server and four replicas. I am trying to figure out why slurpd.replog is
deletedso large lately. This morning we had a 600MiB slurpd.replog. I
replog/var/spool/slapd/replica and rebuilt the slaves manually.
We have "replicationinterval 10" set in slapd.conf and yet the
arenow has 14k of changes. There are no .rej files and the replicas
grow?being updated successfully. What is causing the replog file to
-- Jacob Elder