Reproduce it like this:
modify nsslapd-db-locks under "cn=config,cn=ldbm database,cn=plugins,cn=config"
nsslapd-db-configured-locks under "cn=database,cn=monitor,cn=ldbm database,cn=plugins,cn=config"
and verify the number has not changed.
db_stat -c -h /var/lib/dirsrv/slapd-server3/db/ | grep locks
40002 Maximum number of locks possible
Shows the older value. So, Berkeley db has never been set with the new value.
remove temporary files or guardian file (CONFIRM SERVER IS STOPPED):
and verify the number is the new one.
the changes in db lock configuration should be handled like changes in cache size. value should be stored in the guardian file. at startup, if a guardian file exists, the max locks should be compared with the configured locks and if they are different the env should be recreated
git patch file (master)
Reviewed by Mark (Thank you!!)
Pushed to master:
f724b34..f4437de master -> master
Pushed to 389-ds-base-1.3.3:
87c7b15..dc4185e 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
Pushed to 389-ds-base-1.3.2:
20cb0c0..d1e4698 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
Pushed to 389-ds-base-1.3.1:
bf27455..86b728f 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
Pushed to 389-ds-base-1.2.11:
6b85c3a..295cf31 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 126.96.36.199
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)
to comment on this ticket.