[389-users] Enabling replication with changelog max age
Rich Megginson
rmeggins at redhat.com
Tue Mar 27 14:07:43 UTC 2012
On 03/27/2012 08:06 AM, Reinhard Nappert wrote:
> Hi all,
> I have a couple of question regarding the nsslapd-changelogmaxage
> attribute:
> This attribute sets the maximum age that entries are kept in the
> changelog. Documentation says that a change of the value requires a
> server restart.
> 1. Do I have to restart the server, when I enable replication, where I
> set a value (let's say "30d") during the enabling process - in ldap
> terms, I include nssslapd-changelogmaxage: 30d as an attribute, when
> the entry cn=changelog5, cn=config gets added?
No.
> 2. What happens if I have a changelog (previsously set to unlimited
> age) and I set the value to 30d. Does it remove every entry older than
> 30 days, after the restart. It looks to me that the size of the
> database did not change, because I did not gain any diskspace after I
> restarted the server.
Not sure. You could use the cl-dump tool to examine the changelog.
> Thanks,
> -Reinhard
>
>
> --
> 389 users mailing list
> 389-users at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20120327/ef862fcb/attachment.html>
More information about the 389-users
mailing list