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

RE: replogcopy functionality (ITS#3030)

Unless I missed something, I seem to recall seeing the slurpd.replog file
shrinking as replication was completed.  On my test machines, I've never
removed them and it seemed some process somewhere was managing them, so I
thought this replogcopy would be useful.

I definately see syncrepl replacing slurpd, but at that time, I'm hoping the
master replog file can serve as the untouched replog that this patch hopes
to address.

-----Original Message-----
From: owner-openldap-bugs@OpenLDAP.org
To: openldap-its@OpenLDAP.org
Sent: 3/19/2004 7:47 AM
Subject: Re: replogcopy functionality (ITS#3030)

> Full_Name: Digant C Kasundra
> Version: 2.2.6
> OS: RHEL AS 3.0
> URL:
> ftp://ftp.openldap.org/incoming/digantkasundra-replogcopy-040318.tgz
> Submission from: (NULL) (
> This patch adds new functionality to slurpd.  It allows you to specify
> the statement "replogcopy {filename}" in the slapd.conf file.  When
> slurpd copies over the contents of the master replog file into its own
> replog file, it will also copy the contents into this replogcopy file.
> The intended purpose is to have a replogfile that will remain intact
> other daemons and applications that need to know about changes on the
> master server.

What will be the difference between the replogcopy file and slurpd's
replog?  Slurpd's replog file is not truncated or cancelled for any
reason; actually, its purpose is to remain as a log of all the write
operations performed on the master.  However, I might be missing
Note that slurpd's approach to replication is going to be replaced by
syncrepl at some point in the future.  As such, slurpd is barely
maintained but no development should be dedicated to it.


Pierangelo Masarati