From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b)
Description of problem:
In some situations slapd can be shut down incorrectly and leave the
database lock files behind:
When this happens, slapd hangs without any visible sign on startup,
waiting for the locking to go away.
The ldap start script should check whether these files exist and if
yes, check whether there is a running process. if not, the fiels
should be removed. If this is deemed to dangerous, the a message
should be issued to tell the user about the fact and ask her/him to do it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.probably kill -9 of slapd
(alternatively, create fake __db* files
Actual Results: hangs
Expected Results: starts up
Running "slaptest" first, which times out in these cases, at least prevents the
complete hang in 2.2.13-4 and later. Versions 2.2.26-1 and later re-run with
"-u" to see if read-only access is possible, and if that succeeds, checks for a
the existence of __db.001, and if it's there, presents the warning.