|Previous Contents Index DocHome Next|
|iPlanet Directory Server Configuration, Command, and File Reference|
Chapter 4 Server Instance File Reference
This chapter provides an overview of the files stored under /usr/iplanet/servers/slapd-serverID. Having an overview of the files and configuration information stored in each instance of Directory Server will help you understand the file changes or absence of file changes which occur in the course of directory activity. It will also help you to detect errors and intrusion, by indicating what kind of changes to expect, and as a result, what changes are considered abnormal.
Overview of Directory Server Files
Directory Server files and command-line scripts are stored under installDir/slapd-serverID, where serverID is the server identifier. The only exception is the migrateInstance5 script, which is stored under installDir/bin/slapd/admin/bin.
The following listing shows the contents of installDir/slapd-serverID on a UNIX platform, where directories are marked with a slash (/) and scripts are marked with an asterisk (*). See Chapter 8 "Command-Line Scripts" for further information on command-line Scripts.
Code Example 4-1    Contents of the installDir/slapd-serverID Directory ./ db2ldif* ns-inactivate.pl*
../ db2ldif.pl* restart-slapd*
bak/ getpwenc* restoreconfig*
bak2db* ldif/ saveconfig*
bak2db.pl* ldif2db* start-slapd*
conf_bk/ ldif2db.pl* stop-slapd*
confbak/ ldif2ldap* suffix2instance*
config/ locks/ tmp/
db/ logs/ vlvindex*
To reflect the directory structure under installDir/slapd-serverID, this chapter is divided into the following sections:
Each Directory Server instance contains the following three directories for storing backup related files:
bak - contains a directory dated with the time and date of your database backup, for example 2001_02_13_174524/, which in turn holds your database backup copy.
confbak - is the default directory used by the restoreconfig script and the saveconfig scripts. See Chapter 8 "Command-Line Scripts" for further information on Command-line Scripts.
Each Directory Server instance contains the following directory for storing configuration files:
config - contains the configuration files as explained in "Server Configuration - Overview" on page 23.
Each Directory Server instance contains the db directory for storing all the database files. The following listing shows the sample contents of the db directory.
db.00x files - used internally by the database. Should not be moved, deleted, or modified in any wayThe following listing shows the sample contents of the NetscapeRoot directory.
Code Example 4-3    Sample Contents of the NetscapeRoot Subdirectory ./ entrydn.db3 parentid.db3
../ givenName.db3 sn.db3
aci.db3 id2entry.db3 uid.db3
cn.db3 nsUniqueId.db3 uniquemember.db3
The NetscapeRoot subdirectories contain an index_name.db3 file for every index currently defined in the database, where index_name is the name of the index. In addition to these index_name.db3 files, the Netscape and userRoot subdirectories contain the following files:
dncomp.db3 - contains a list of partial DNs enabling you to find IDs.
Each Directory Server instance contains the ldif directory for storing ldif related files. The following listing shows the sample contents of the ldif directory.
The following list describes the content of each of the ldif files:
European.ldif - contains European character samples.
Siroe-roles.ldif - is a sample ldif file similar to Siroe.ldif except that it uses roles and class of service instead of groups for setting access control and resource limits for Directory Administrators.
Each Directory Server instance contains a locks directory for storing lock related files. The following listing shows the sample contents of the locks directory.
The lock mechanisms stored under the locks subdirectories exports, imports, and server prevent simultaneous operations from conflicting with each other. The lock mechanisms allow for one server instance to run at a time, with possible multiple export jobs. They also permit one ldif2db import operation (or one directoryserver ldif2db operation on Solaris 9 platforms) at a time to the exclusion of all export and slapd server operations.
This restriction does not apply to the ldif2db.pl script (directoryserver ldif2db-task on Solaris 9 platforms), since you can run multiple ldif2db.pl operations at any time.
Each Directory Server instance contains a logs directory for storing log related files. Code Example 4-6 shows a sample listing of the logs directory contents.
Code Example 4-6    Contents of a sample logs directory
./ access.20010126-120123 audit errors.rotationinfo
../ access.20010130-140221 audit.rotationinfo pid
access access.20010201-100122 errors slapd.stats
access.20010124-180611 access.rotationinfo errors.20010124-180607
The following list describes the content of the log related files:
The content of the access, audit and error log files is dependent on the log configuration.
The slapd.stats file is a memory-mapped file which cannot be read by an editor. It contains data collected by the Directory Server SNMP data collection component. This data is read by the SNMP subagent in response to SNMP attribute queries and is communicated to the SNMP master agent responsible for handling Directory Server SNMP requests.
Previous Contents Index DocHome Next
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.
Last Updated October 29, 2001