Bug 985494 - clarify what locks are stored in the locks directory
clarify what locks are stored in the locks directory
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-administration-guide (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Deon Ballard
Jenny Galipeau
Depends On:
  Show dependency treegraph
Reported: 2013-07-17 11:42 EDT by Rich Megginson
Modified: 2014-07-29 16:43 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-07-29 16:43:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rich Megginson 2013-07-17 11:42:34 EDT
Description of problem:

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:

Actual results:

Expected results:

Additional info:
Comment 1 Deon Ballard 2014-07-29 16:43:37 EDT
Mass closure of published bugs.

Note You need to log in before you can comment on or make changes to this bug.