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

Hide thumbs Also See for DIRECTORY SERVER 8.1 - RELEASE NOTES:
Table of Contents

Advertisement

Red Hat Directory Server 8.1 Release Notes
1.7. Extended Get Effective Rights Operations with Options for Non-
Existent and Operational Attributes
A get effective rights operation is an extended ldapsearch that, along with regular search results,
returns that access permissions that one directory user has to a directory entry or entries.
Directory Server 8.1 adds two additional attribute search options for get effective rights searches. One
(*) returns rights for non-existent attributes for the entry, meaning attributes which could be set on the
entry but currently are not. The other (+) returns access rights for operational attributes for the entry.
1.8. Added New Support for 64-Bit Integers for Performance
Counters on 32-Bit Systems
Many of the performance counters for the Directory Server — including server statistics, database
statistics, and SNMP monitoring — record 32-bit integers. For large or high-traffic systems, these
counters may roll over too quickly, creating quirky performance statistics and making it difficult to
conduct long-term analysis.
Directory Server 8.1 introduces support for 64-bit integers for performance counters, even on 32-
bit systems. These 64-bit integers are enabled through a new configuration attribute on the DSE,
nsslapd-counters. When 64-bit integers are enabled, all available counters support 64-bit integers.
For server statistics, there are five counters which support 64-bit integers:
• opsinitiated
• opscompleted
• entriessent
• bytessent
• totalConnections
For database statistics, there are four counters which support 64-bit integers:
• entrycachehits
• entrycachetries
• currententrycachesize
• maxentrycachesize
All of the attributes monitored by SNMP can support 64-bit integers.
1.9. Added New Parameter for Setting the Interval for Win Sync
Checks
In synchronization, updates are sent two ways, from the Directory Server to the Active Directory
server and from Active Directory back to the Directory Server. The frequency which Directory
Server sends updates to Active Directory is set in the synchronization schedule, handled by the
nsds5replicaupdateschedule attribute. The frequency which Directory Server checked Active
Directory for updates was hard coded at five minutes.
4

Advertisement

Table of Contents
loading

Table of Contents