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

Red Hat Directory Server 8.1 Release Notes
Bug Number Description
Some standard schema were removed between Directory Server 7.1 and Directory
Server 8.0 and 8.1. Then, during migration, some of these deprecated schema
elements were migrated to the new version (because they had been replicated)
but other elements mentioned in the schema definitions were still missing, so the
99user.ldif file was invalid. This caused migration to fail.
445775 Many standard schema elements have empty descriptions (DESC ''). However,
474254 any schema element with an empty description was treated as a custom element
and was replicated into the 99user.ldif file on a consumer server. Therefore,
many standard schema elements were replicated.
447353 The Directory Server limited indexed searches to a minimum of three characters.
This meant that a substring search such as ab* was indexed and completed very
quickly, but a search such as a* was unindexed and could take a long time.
In some cases, it's necessary to have indexed searches for very short strings, even
though there is a performance hit. A new attribute, nsSubStrLen, was added to
reset the minimum search string length for an index.
450046 If the ns-slapd process stopped uncleanly while the server was writing to
the changelog, the changelog writes would hang when the ns-slapd process
restarted, unless the entire system was rebooted.
450575 If an operation was opened with unsupported critical controls, then the operation
wasn't closed with an unbind or abandon request, and the connection stayed open.
450941 The Directory Server configuration scripts check whether the requested ports are
available before continuing the installation. However, the scripts did not reset the
available ports after an instance was removed, so configuring additional instance
on the same server could incorrectly return that a port was unavailable when, in
fact, it was free.
452007 When an instance was removed, its directories were renamed
slapd-instance.removed. However, when the start script was run without giving
a specific instance (service dirsrv start), then the start script still picked up
the removed instance and attempted to start it. This resulted in an error, that the
removed server couldn't be started.
The removed instance directory are now named removed.slapd-instance, so the
removed instance is ignored by the start scripts and there are no more confusing
error messages.
452328 If a range set in an ldapsearch had a different number of digits in the lower and
upper bounds, the search would not return the right results. For example, this
command would not return any entries, even though entries existed within that
range:
ldapsearch -D "cn=directory manager" -w secret -b
"dc=example,dc=com" "(&(uidNumber>=7)(uidNumber<=12))"
452569 By default, 64-bit Red Hat Enterprise Linux systems expected the SASL libraries
to be in /usr/lib/sasl2, rather than /usr/lib64/sasl2. This meant that it
printed spurious errors to the Administration Server error logs about being unable
to locate the SASL libraries.
18