Exa mple 4 .2. Netscape Root Database Directory Content s
./ entrydn.db4* parentid.db4*
../ givenNam e.db4* sn.db4*
DBVERSION* id2entry.db4* uid.db4*
aci.db4* nsUniqueId.db4* uniquem ember.db4*
ancestorid.db4* numsubordinates.db4*
cn.db4* objectclass.db4*
The NetscapeRoot subdirectories contain an index_namedb4 file for every index currently defined in
the database. In addition to these files, the NetscapeRoot and userRoot subdirectories contain the
following files:
ancestorid.db4 — Contains a list of IDs to find the ID of the entry's ancestor.
entrydn.db4 — Contains a list of full DNs to find any ID.
id2entry.db4 — Contains the actual directory database entries. All other database files can be
recreated from this one, if necessary.
nsuniqueid.db4 — Contains a list of unique IDs to find any ID.
numsubordinates.db4 — Contains IDs that have child entries.
objectclass.db4 — Contains a list of IDs which have a particular object class.
parentid.db4 — Contains a list of IDs to find the ID of the parent.
4.5. LDIF Files
Sample LDIF files are stored in the /var/lib/dirsrv/slapd-instance_name/ldif directory for
storing LDIF-related files. Example 4.3, “LDIF Directory Contents” lists the /ldif directory contents.
Exa mple 4 .3. LDIF Dire ctory Content s
European.ldif
Exam ple.ldif
Exam ple-roles.ldif
Exam ple-views.ldif
European.ldif — Contains European character samples.
Exam ple.ldif — Is a sample LDIF file.
Exam ple-roles.ldif — Is a sample LDIF file similar to Exam ple.ldif, except that it uses roles
and class of service instead of groups for setting access control and resource limits for directory
administrators.
NOTE
The LDIF files exported by db2ldif or db2ldif.pl scripts in the instance directory are stored
in /var/lib/dirsrv/slapd-instance_name/ldif.
4.6. Lock Files
Each Directory Server instance contains a /var/lock/dirsrv/slapd-instance_name directory for
storing lock-related files. The following is a sample listing of the locks directory contents.
Exa mple 4 .4 . Lock Directory Content s
exports/ im ports/ server/
The lock mechanisms stored in the exports, im ports, and server subdirectories prevent multiple,
simultaneous operations from conflicting with each other. T he lock mechanisms allow for one server
instance to run at a time, with possible multiple export jobs. T hey also permit one ldif2db import
operation at a time (not ldif2db.pl, because multiple ldif2db.pl operations can be run at any
time) to the exclusion of all export and slapd server operations.
If there are error messages indicating that the lock table is out of available locks (for example, libdb:
To Next Page