Red Hat DIRECTORY SERVER 8.1 - RELEASE NOTES Release Note page 20

Red Hat Directory Server 8.1 Release Notes
Bug Number Description
469800 The import process for large databases could be extremely slow is the databases
contained a large number of non-leaf entries because of how ling it took to create
the ancestorid index.
470393 Setting the nsslapd-timelimit configuration attribute to -1 was rejected, even
though that setting should have been allowed to set an infinite time limit.
470611 The rsearch tool had pre-defined filters and passwords to use for "search then
bind" tests. Two new arguments have been added to allow users to define their own
filter and password.
470918 If two supplier bind DNs were added to the database using an ldapmodify
request, then replication using the second or subsequent bind DN failed.
470946 If the Administration Server was configured to use SSL, the Console would save
its server certificate to its console.conf file without putting quotes around the
certificate name. If the certificate name had spaces in it, the Administration Server
was then unable to restart.
471138 The ldclt tool was enhanced to perform abandon operations.
471998 The dbverify tool could not process integer-based sorting, but it was possible
to configure an index with numeric sorting by setting nsMatchingRule:
integerOrderingMatch. The dbverify tool has been extended to include
numeric sorting.
472457 If a custom server-side sorting order was used and then the database was indexed,
then the Directory Server could crash or become unresponsive under certain
circumstances.
474237 If a suffix was exported that had subsuffixes, then erroneous and confusing
error messages were printed during the export claiming that (parent) instance
already existed as it processed the subsuffix entries. The db2ldif -s
command has be modified so that it checks for the parent DN of every suffix
it processes. This also enabled the script to be run on a branch point, like
ou=groups,dc=example,dc=com, successfully because the script moves up the
directory tree until it finds the suffix to export.
474248 If replication was set up for a backend which did not exist on the consumer, then
the consumer Directory Server would crash as soon as the supplier tried to initialize
the consumer.
474621 When adding a user-specified nsUniqueID value for a new entry, the Directory
Server would reject the value and use an auto-generated nsUniqueID value.
However, if nsUniqueID was used as the RDN, the original user-supplied
nsUniqueID value was still used in the DN, even though that value didn't exist in
the entry.
474729 Some search results which contained unindexed attributes did not contain the
notes=U message in the access log, to indicate an unindexed search.
475338 The nsslapd-*log-logmaxdiskspace, nsslapd-*log-
logminfreediskspace, and nsslapd-*log-maxlogsize configuration
attributes accept sizes in megabytes, but the values were converted to bytes in the
backend. Using 32-bit integers for the sizes overflowed easily. These configuration
attributes have been changed to handle 64-bit integers.
475899 An extensible match filter is used as part of an LDAP that instructs
the server what kind of matching rule to use. For example,
20