Bug 135483 - openldap offer a context cn=config even if no back-config is given
Summary: openldap offer a context cn=config even if no back-config is given
Status: RESOLVED INVALID
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Network (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Ralf Haferkamp
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-24 14:54 UTC by Dennis Sieben
Modified: 2006-02-17 15:19 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Sieben 2005-11-24 14:54:47 UTC 
When slapd is startet with the paramter -f filename, it generates a pseudo back-config structure below cn=config even if no back-config database directory is there. The only thing which is essential for this to happen is the entry database config in the slapd.conf file.
Comment 1 Ralf Haferkamp 2006-02-17 15:13:42 UTC 
I talk to the developers about this. This is done by intention. back-config is always present (even if you leave away the "database config"  directive from slapd.conf).
If, as in your case, the back-config database directory does not exist, back-config will work as usual, with the only difference that changes to the configuration are not persitent after restart of the daemon.
See also the thread on openldap-devel:
http://www.openldap.org/lists/openldap-devel/200602/msg00013.html
Comment 2 Ralf Haferkamp 2006-02-17 15:19:27 UTC 
So this is "invalid".