Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1450893
Description of problem: When nsslapd-cache-autosize is not set in dse.ldif, ldapsearch does not show the default value. [root@qe-blade-01 ~]# ldapsearch -h 127.0.0.1 -b "cn=config" -D "cn=Directory Manager" -w Secret123 nsslapd-cache-autosize nsslapd-dbcachesize |grep -e nsslapd-cache-autosize -e nsslapd-dbcachesize # requesting: nsslapd-cache-autosize nsslapd-dbcachesize nsslapd-dbcachesize: 160999144 The ldapsearch command output only shows the optimized "nsslapd-dbcachesize" values. Version-Release number of selected component (if applicable): 389-ds-base-1.3.6.1-13.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Login into freshly installed dirsrv instance. 2. Search for "nsslapd-cache-autosize" parameter using ldapsearch command. Actual results: Ldapsearch does not show default nsslapd-cache-autosize value. Expected results: Ldapsearch should show default nsslapd-cache-autosize value. Additional info:
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1450893
Metadata Update from @mreynolds: - Issue assigned to mreynolds
Fixed in issue 49258
Metadata Update from @mreynolds: - Custom field type adjusted to defect - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
Metadata Update from @vashirov: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: None (was: 0.0 NEEDS_TRIAGE)
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: - https://github.com/389ds/389-ds-base/issues/2318
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: duplicate)
Login to comment on this ticket.