Description of problem:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Configuration_Command_and_File_Reference/Server_Instance_File_Reference-Lock_Files.html

The documentation is confused about the purpose of the locks directory.  The locks directory controls how many copies of the directory server process can be running at once.

When there is an import job running (ldif2db - note: this does not apply to ldif2db.pl), there can be no other ns-slapd, ldif2db, or db2ldif process running.  A lock is placed in the imports/ directory - this prevents a lock being placed in the exports or server directory.

When the server is running normally - a lock is placed in the server/ directory.  This prevents ldif2db from running but allows db2ldif.

When db2ldif is running - a lock is placed in the exports/ directory.  This allows the server to run normally but prevents ldif2db.

The other stuff about the database that begins with "If there are error messages indicating that the lock table is out of available locks . . " should go into the database configuration and monitoring section.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: