Red Hat Directory Server 8.0 Configuration, Command, and File Reference

be modified with the guidance of Red Hat Technical Support or Red Hat Professional Services.
Parameter Description
Entry DN cn=config, cn=ldbm database, cn=plugins,
cn=config
Valid Values on | off
Default Value on
Syntax DirectoryString
Example nsslapd-db-circular-logging: on
4.1.8. nsslapd-db-debug
This attribute specifies whether additional error information is to be reported to Directory Server.
To report error information, set the parameter to on. This parameter is meant for
troubleshooting; enabling the parameter may slow down the Directory Server.
Parameter Description
Entry DN cn=config, cn=ldbm database, cn=plugins,
cn=config
Valid Values on | off
Default Value off
Syntax DirectoryString
Example nsslapd-db-debug: off
4.1.9. nsslapd-db-durable-transactions
This attribute sets whether database transaction log entries are immediately written to the disk.
The database transaction log contains a sequential listing of all recent database operations and
is used for database recovery only. With durable transactions enabled, every directory change
will always be physically recorded in the log file and, therefore, able to be recovered in the event
of a system failure. However, the durable transactions feature may also slow the performance of
the Directory Server. When durable transactions is disabled, all transactions are logically written
to the database transaction log but may not be physically written to disk immediately. If there
were a system failure before a directory change was physically written to disk, that change
would not be recoverable. The nsslapd-db-durable-transactions attribute is absent from
dse.ldif. To disable durable transactions, add the attribute to dse.ldif.
This attribute is provided only for system modification/diagnostics and should be changed only
with the guidance of Red Hat Technical Support or Red Hat Professional Services. Inconsistent
settings of this attribute and other configuration attributes may cause the Directory Server to be
unstable.
For more information on database transaction logging, refer to the "Monitoring Server and
Chapter 3. Plug-in Implemented Server Functionality Reference
136