#244 allow nsslapd-idlistscanlimit to be set dynamically and per-user
Closed: wontfix None Opened 10 years ago by rmeggins.


Unable to change nsslapd-idlistscanlimit in a running server.
Unable to set per-user idlistscanlimit (as with nsLookThroughLimit)

commit changeset:c21515b/389-ds-base
Author: Rich Megginson rmeggins@redhat.com
Date: Thu Sep 29 11:36:20 2011 -0600
Reviewed by: nhosoi, nkinder (Thanks!)
Branch: master
Fix Description: Changed the ldbm_config for idlistscanlimit to allow runnin
change. Added a new attribute nsIDListScanLimit that works just like
nsLookThroughLimit for user entries. For each search operation, calculate
the idlistscanlimit to use based on any nsIDListScanLimit or database config
The biggest change was to extend the internal database API to allow the
idlistscanlimit (aka allidslimit) to be passed down into the lowest level of
the code where it is used.
Platforms tested: RHEL6 x86_64
Flag Day: no
Doc impact: Yes - will need to document how nsIDListScanLimit and
nsslapd-idlistscanlimit work now

Added initial screened field value.

Metadata Update from @nkinder:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.2.10

5 years ago

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

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)

2 years ago

Login to comment on this ticket.