RE: replogcopy functionality (ITS#3030)

[digant@uta.edu]

If the intent of the replogfile is simply to provide information to the
replication service (slurpd) than perhaps it isn't a flaw that slurpd clear
the log when it is done with the information.  But since a preserved track
of the changes would be valuable, the replogcopy feature would address that
need.

-----Original Message-----
From: owner-openldap-bugs@OpenLDAP.org
To: openldap-its@OpenLDAP.org
Sent: 3/24/2004 4:18 PM
Subject: Re: replogcopy functionality (ITS#3030)


> Ando,
>
> That is not how the replog's work at all:
>
> slapd writes a replog file.
>
> slurpd reads that replog file, and zero's it out, and writes its own
> copy.
>
> slurpd passes the changes on to the replica's.  After the changes in
the
>  file have been passed on, it deletes all but the last few changes
that
> the  replica's have received.  Thus, <all> changes are *not* kept over
> time.

OK, then I must have missed that; I would then consider this a flaw,
because there should be a track of the changes being made to the server
over time.