Red Hat DIRECTORY SERVER 7.1 Manual do Utilizador descarregar pdf (Página 9)

Bug Number Description

back with its original ntUniqueId value, but

Active Directory uses a DN-based GUID, so

re-adding the entry failed with a naming

violation.

In Directory Server 8.0, Windows Sync has

been enhanced to better deal with

resurrecting tombstone entries in Active

Directory. On Active Directory 2000, the entry

is resurrected with a new GUID; on Active

Directory 2003, the entry is resurrected with

the original GUID. In both cases, the

resurrected entry retains all of its original

attributes and values.

243820

When Directory Server was shut down, the

active browsing index was interrupted; rather

than closing cleanly, the file was corrupted.

Trying to delete the index failed because the

Directory Server did not recognize the corrupt

file, but trying to recreate the index also failed

because the corrupt file caused the process to

hang.

Directory Server 8.0 shuts down the active

browsing index, it closes cleanly, and if an

error occurs, it removes the index file

successfully.

247725 If the RDN of an entry ended in a double

backslash (\\), then Directory Server would

crash when an LDIF containing that entry was

imported. This has been fixed.

249366

If an attribute with INTEGER syntax was longer

than the 32-bit limit, ldapsearch filters could

return entries which did not match the search

criteria. because Directory Server versions

7.1 and earlier allowed search filters on all

INTEGER syntax attributes by default.

However, this violated the LDAPv3 definition

for INTEGER syntax attributes.

Directory Server 8.0 disallows range searches

on indexed integer-valued attributes by

default. There are two ways this can be

Bugs Fixed in Directory Server 8.0

9

1 2 3 4 5 6 7 8 9 10 11 12 13 14

Comentários a estes Manuais

Sem comentários