[bug-notifications] [openldap 0004521]: openldaprc file is missing, slapd.conf not found by service start method

[Mantis Bug Tracker]

The following issue has been ASSIGNED. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4521 
====================================================================== 
Reported By:                dorix
Assigned To:                dam
====================================================================== 
Project:                    openldap
Issue ID:                   4521
Category:                   packaging
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2010-08-13 22:43 CEST
Last Modified:              2010-11-23 15:14 CET
====================================================================== 
Summary:                    openldaprc file is missing, slapd.conf not found by
service start method
Description: 
A fresh install of CSWopenldap 2.4.22,REV=2010.06.08 on a new zone
immediately comes up in maintenance state.  The service start method looks
for the non-existent openldaprc file in /etc/opt/csw and /opt/csw/etc,
fails to find it, and tries to fall back on the now-incorrect default
location for slapd.conf and slapd.d: /opt/csw/etc/openldap/slapd.conf and
/opt/csw/etc/openldap/slapd.d.

Comments in /var/opt/csw/svc/method/svc-cswopenldap say to copy the
openldaprc template file from /opt/csw/share/doc/openldap to /etc/opt/csw,
but there is no openldaprc template file in /opt/csw/share/doc/openldap.
====================================================================== 

---------------------------------------------------------------------- 
 (0008382) gadavis (developer) - 2010-10-20 00:00
 https://www.opencsw.org/mantis/view.php?id=4521#c8382 
---------------------------------------------------------------------- 
+1 for a fix, this was a frustrating bug to stumble upon.