#48214 ldapsearch on nsslapd-maxbersize returns 0 instead of current value
Closed: wontfix Opened by nhosoi.

Description of problem:
ldapsearch on nsslapd-maxbersize returns 0
How reproducible:
always
Steps to Reproduce:
1. ldapsearch -LLLx -D "cn=Directory Manager" -W -b "cn=config"
nsslapd-maxbersize | grep nsslapd-maxbersize
Actual results:
nsslapd-maxbersize: 0
Expected results:
nsslapd-maxbersize should report current value
Additional info:
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/
Configuration_Command_and_File_Reference/Core_Server_Configuration_Reference.ht
ml#cnconfig-nsslapd_maxbersize_Maximum_Message_Size
Zero 0 means that the default value should be used.

{{{

142 142 #define DEFAULT_MAXBERSIZE 2097152
143 #define DEFAULT_MAXBERSIZE_STR "2097152"
}}}
Don't define DEFAULT_MAXBERSIZE_STR. Use STRINGIFYDEFINE:
{{{
CONFIG_INT, NULL, STRINGIFYDEFINE(DEFAULT_MAXBERSIZE)},
}}}

otherwise, ack

git patch file (master) -- fixed the patch as suggeted by Rich in comment:2. (Thank you, Rich!)
0001-Ticket-48214-ldapsearch-on-nsslapd-maxbersize-return.patch

Reviewed by Rich (Thank you!!)

Pushed to master:
a533145..b7b663c master -> master
commit 7d0689aaadfa66a8f8a481b0c1bb70b2465c4986
commit b7b663c0e20c2f9bf8885bd7633570dc8d34f394

Pushed to 389-ds-base-1.3.4:
0e079ab..7c73adc 389-ds-base-1.3.4 -> 389-ds-base-1.3.4
commit b83c2554fad0bb2a08055c5105bcfa4c9d44af8f
commit 7c73adc28c8877eb3b0d30a91f7fa8a964fb3fd2

Metadata Update from @rmeggins:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.4.2

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/1545

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)

Metadata