diff options
| author | Garming Sam <garming@catalyst.net.nz> | 2019-02-28 16:21:57 +1300 |
|---|---|---|
| committer | Karolin Seeger <kseeger@samba.org> | 2019-03-05 19:29:15 +0000 |
| commit | a65f7b71a2533b393e4d150fc1d0b07576dd95a0 (patch) | |
| tree | 3c0565b951970ea970fa0c8924b8edb7db12cbe1 /WHATSNEW.txt | |
| parent | 3fe0c3031e6cc4848e069c7ab916ac79d7f2692c (diff) | |
| download | samba-a65f7b71a2533b393e4d150fc1d0b07576dd95a0.tar.gz | |
WHATSNEW: Add some detail on the changes to paged results
Signed-off-by: Garming Sam <garming@catalyst.net.nz>
Diffstat (limited to 'WHATSNEW.txt')
| -rw-r--r-- | WHATSNEW.txt | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/WHATSNEW.txt b/WHATSNEW.txt index 716e4621b75..50183f72181 100644 --- a/WHATSNEW.txt +++ b/WHATSNEW.txt @@ -63,6 +63,24 @@ information about how the users are spread across groups in your domain. The 'samba-tool group list --verbose' command has also been updated to include the number of users in each group. +Paged results LDAP control +-------------------------- + +The behaviour of the paged results control (1.2.840.113556.1.4.319, RFC2696) +has been changed to more closely match Windows servers, to improve memory +usage. Paged results may be used internally (or is requested by the user) by +LDAP libraries or tools that deal with large result sizes, for example, when +listing all the objects in the database. + +Previously, results were returned as a snapshot of the database but now, +some changes made to the set of results while paging may be reflected in the +responses. If strict inter-record consistency is required in answers (which is +not possible on Windows with large result sets), consider avoiding the paged +results control or alternatively, it might be possible to enforce restrictions +using the LDAP filter expression. + +For further details see https://wiki.samba.org/index.php/Paged_Results + Prefork process restart ----------------------- |