Bug 967560

Summary: Minor mistakes in the OpenLDAP section
Product: Red Hat Enterprise Linux 6 Reporter: Jan Synacek <jsynacek>
Component: doc-Deployment_GuideAssignee: Jaromir Hradilek <jhradile>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4CC: alyoung, jsynacek
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-02 22:28:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Synacek 2013-05-27 13:10:05 UTC
Document URL: 
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Directory_Servers.html#s1-OpenLDAP

Section Number and Name: 
17.1.3. Configuring an OpenLDAP Server

Describe the issue: 
The very first sentence under the Table 17.5 says:
"Note that OpenLDAP no longer reads its configuration from the /etc/openldap/slapd.conf file."

This is not true. The slapd daemon reads from this file if there is no /etc/openldap/slapd.d directory (meaning that the newer and officially supported documentation format is not used; the old deprecated slapd.conf is used instead). If both are present, slapd.d configuration will be used.

Also, another sentence says:
"If you have an existing slapd.conf file from a previous installation, you can convert it to the new format by running the following command:"

I would add that this conversion is done automatically during updates when slapd.conf is found and slapd.d is not. When this conversion is done during an update, slapd.conf is renamed to slapd.conf.bak.

Suggestions for improvement: 
See above. Feel free to improve the wording;)

Comment 1 Jaromir Hradilek 2013-05-27 14:13:20 UTC
Thank you very much for taking the time to report this issue!