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

Bug Number Description
430321 There was a memory leak in the collation plug-in.
430364 The setup-ds-admin.pl script did not correctly set the IP address of the
Administration Server if the Administration Server IP address was different than the
Directory Server instance's IP address.
430368 When configuring a new instance with setup-ds.pl, the server could fail to start
432135 because it couldn't open the /var/run/dirsrv/ directory and, therefore, open
the stats file for the instance.
430568 It is possible to specify which locale to use when running an ldapsearch.
Specifying the default locale (2.16.840.1.113730.3.3.2.0.1), however,
returned spurious errors to the log, saying that the collation mode and strength
could not be set, even though they were.
430993 The log deletion policies set for the access, audit, and error logs could be ignored
if the two parameters defining the time amount (integer) and time unit (day, week,
month, or year) are not in the proper order. In dse.ldif, the time amount had to
be listed first, then the time unit next.
Changing only one of the defaults for the deletion policy in the Directory Server
Console added only that one parameter to the dse.ldif file. If only one of the
parameters was in the file, than the nsslapd-TYPElog-logexpirationtime defaulted
to not expiring (PR_INT32_MAX) and nsslapd-TYPElog-logexpirationtimeunit to
seconds.
431607 The Referential Integrity Plug-in did not ignore spaces in DNs.
So, it treated ou=groups, dc=example, dc=com as different
than ou=groups,dc=example,dc=com. However, the plug-in
would insert white spaces into DNs during a rename operation, so if
ou=groups,dc=example,dc=com was added to the database, the Referential
Integrity Plug-in would change it to ou=groups, dc=example, dc=com. This
would then break referential integrity.
435774 When trying to install a new instance of Directory Server using setup-ds.pl
and specifying an input file to import to populate the databases, the script failed
with an error that it could not import LDIF file. The new instance was only partially
configured, and had to be removed and re-installed.
435778 The ds_removal script assumed that any instance being removed was fully
configured and running. Therefore, when trying to remove an instance where the
setup had failed, the configuration had become corrupted, or that was off would fail
with this error:
Error:The server '' is not reachable. Error: unknown error
437049 If the inherited object classes were not explicitly set in an entry, the supplier server
would show that the entry had the inherited object classes, but the replicated on the
entry in the consumer server would not have the inherited object classes. Inherited
object classes were not replicated.
438139 Rename operations failed if the RDN contained a backslash (\).
445305 Trying to create a second Directory Server instance on a server would fail if its Unix
user and group IDs were different than the first instance's Unix user and group IDs.
445602 Because schema with an empty description was treated as user-defined, some
standard schema elements were replicated into consumers' 99user.ldif files.
Bugs Fixed in 8.1
17