Re: replogcopy functionality (ITS#3030)

[ando@sys-net.it]

> 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.

p.

-- 
Pierangelo Masarati
mailto:pierangelo.masarati@sys-net.it