Hi William,

With autosizing on I configured the changelog backend:

dn: cn=changelog,cn=ldbm database,cn=plugins,cn=config
cn: changelog
objectClass: top
objectClass: extensibleObject
objectClass: nsBackendInstance
nsslapd-suffix: cn=changelog
nsslapd-cachesize: -1
nsslapd-cachememsize: 8858370048
nsslapd-readonly: off
nsslapd-require-index: off
nsslapd-directory: /var/lib/dirsrv/slapd-CNVR-NET/db/changelog
nsslapd-dncachememsize: 3000000000

Here’s the ldif:

dn: cn=changelog,cn=ldbm database,cn=plugins,cn=config
changetype: modify
replace: nsslapd-dncachememsize
nsslapd-dncachememsize: 3000000000
replace: nsslapd-cachememsize
nsslapd-cachememsize: 3000000000

The server refused to change nsslapd-cachememsize because of autosizing but 
nsslapd-dncachememsize did get changed. So it seems that I can still control 
nsslapd-dncachememsize? When I restart 389-ds, the 3G persists as well.

Does that make sense?

Thank you for a quick response!


> On Mar 13, 2018, at 7:40 PM, William Brown <will...@blackhats.net.au> wrote:
> If autosize > 0, we write a new entrychace/cachememsize every start up.
> So you only need to set autosize to between 1 and 99 for it to work.
> There is some other logic in there to account for other scenarioes =
> for example, if you set autosize to 0 AND you set the entry cachesize
> to 0, we'll autosize it at start up anyway. BUT if you have autosize =
> 0, and entry cachesize > 0, we won't touch it.

389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

Reply via email to