Description of problem:
No validation check for the value for nsslapd-db-locks.
nsslapd-db-configured-locks takes any value.
A range of value should be accepted and values should be validated.
git patch file (master)
[17/Dec/2015:14:09:00 +1000] - 389-Directory/1.3.5 B2015.351.42 starting up
[17/Dec/2015:14:09:00 +1000] - New max db lock count is too small. Resetting it to the default value 10000.
Works correctly, passes asan. Ack from me.
Reviewed by William (Thank you!!)
Pushed to master:
f132cf4..f5b9053 master -> master
Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.5 backlog
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.