This section describes the file layout you find after creating a Directory Server instance. The instance-path is the file system path where you created the instance.
This section does not cover the following deprecated scripts, generated for backwards compatibility:
If you do not use the scripts, you can safely remove them.
NSS certificate mapping configuration file.
Each directory database backup is held in its own file system directory. The name of the backup directory corresponds to the time and date of the backup.
Default configuration backup directory provided for you to backup up versions of your configuration.
Default server configuration backup directory.
This directory contains a backup copy of the original Directory Server configuration file, dse.ldif, generated when the server instance was created. This copy can be compared with the current configuration file for troubleshooting.
Server configuration file, not intended to be edited directly.
LDAP schema configuration files. See dirserv(5dssd).
Files used internally by the database. Do not move, delete, or modify these files.
File that identifies the version of the database.
File used to store information about the state of the database, used to determine whether database recovery is required.
Files used to store the database transaction logs.
Files that store your directory suffix information. The directory name is derived from the suffix name, such that the database for a suffix identified by DN dc=example,dc=com is stored in a file system directory named example.
For every index defined in the database, the suffix directory contains a file with a name of the form suffix_indexedAttr.db3, such that an index of CNs for dc=example,dc=com has file name example_cn.db3.
Suffix directories also contain a file named suffix_id2entry.db3. The suffix_id2entry.db3 file contains the directory database entries.
If necessary, all index files can be rebuild from the suffix_id2entry.db3 file. To recreate the index files, reindex the suffix.
Lock files stored here in subdirectories exports/, imports/, and server/ prevent simultaneous operations from conflicting with each other. The lock mechanisms allow one server instance to run at a time. The lock mechanisms also permit only one dsadm import (offline import) operation at a time. As a result, no export or server instance operations can be run during import.
The lock restriction does not however apply to dsconf import (online import) operations. Multiple online imports can run at the same time.
This file records information about client access to Directory Server. For detail about access logs, see Access Logs.
This file records information about modifications to Directory Server data. For detail about audit logs, see Audit Logs.
By default, server core files are dumped here during a crash.
This file records errors, warnings, and informational messages logged during Directory Server operation. For detail about errors logs, see Error Logs.
This file holds the process identifier of the running server.
This memory mapped-file cannot be read in an editor. The slapd.stats file contains data collected for SNMP, which is communicated to the agent responsible for handling SNMP requests.
Plug-in signatures directory, not intended to be used directly.
Server runtime files directory, not intended to be used directly.