For access logging to be enabled, the nsslapd-accesslogattribute must contain a valid path, and the nsslapd-accesslog-logging-enabledconfiguration attribute must be switched to on. Table 2-2lists the four possible combinations of values for these two configuration attributes and their outcome in terms of disabling or enabling of access logging.

Table 2-2 Attribute values for enabling or disabling access logging

 

Value of the

 

Value of the nsslapd-accesslog

nsslapd-accesslog-logging-enabled

 

attribute

attribute

Resulting logging state

 

 

 

empty string

on

Disabled

 

 

 

filename

on

Enabled

 

 

 

empty string

off

Disabled

 

 

 

filename

off

Disabled

 

 

 

2.3.1.2 nsslapd-accesslog-level (Access log level)

This attribute controls what is logged to the access log.

Parameter

Description

 

Entry DN

cn=config

 

 

 

Valid Values

0

No access logging

 

4

Logging for internal access operations

 

256

Logging for connections, operations, and results

 

512

Logging for access to an entry and referrals

 

131072

Provides microsecond operation timing

 

These values can be added together to provide the exact type of logging required; for

 

example, 516 (4 + 512) to obtain internal access operation, entry access, and referral logging.

 

 

 

Default Value

256

 

 

 

 

Syntax

Integer

 

 

 

Example

nsslapd-accesslog-level: 256

 

 

 

2.3.1.3 nsslapd-accesslog-list (List of access log files)

This read-only attribute, which cannot be set, provides a list of access log files used in access log rotation.

Parameter

Description

Entry DN

cn=config

 

 

Valid Values

 

 

 

Default Value

None

 

 

Syntax

DirectoryString

 

 

Example

nsslapd-accesslog-list: accesslog2,accesslog3

 

 

2.3.1.4 nsslapd-accesslog-logbuffering (Log buffering)

When set to off, the server writes all access log entries directly to disk. Buffering allows the server to use access logging even when under a heavy load without significantly impacting performance. However, when debugging, it is sometimes useful to disable buffering in order to see the operations and their results right away instead of having to wait for the log entries to be

24 Core server configuration reference