[Date Prev][Date Next]
Re: LDAP browsers and cn=config
On 07/03/11 21:33, Howard Chu wrote:
Gervase Markham wrote:
On 07/03/11 17:49, Gervase Markham wrote:
And that would be the problem :-|
Thank you for your help.<shuffles feet in an embarrassed fashion>
cn=config is an LDAP database, it is not a collection of files for you
to edit by hand.
Although presumably if you manage to mess up your configuration enough,
that's what you have to do. I've seen "you can edit the files by hand if
it all goes wrong" used as an argument for using the LDIF backend for
cn=config in the archives of this very mailing list, if I'm not mistaken.
You are supposed to use ldapmodify on it, for reasons
of this very nature. I.e., ldapmodify gets syntax-checked and stupid
typos of this sort get caught.
But being able to edit the database is precisely the problem I had! It's
rather chicken and egg.
If you had used "ldapmodify -H ldapi:/// -Y EXTERNAL" to add the desired
attributes you wouldn't have these silly problems.
Yes, of course - because Real Men use commands with a minimum of 4
command-line flags to do any operation, and if I'm not up to that, I
can't possibly be worthy to use OpenLDAP.
If your LDAP browsers don't support ldapi:/// that's their deficiency...
I don't even know what the "i" in ldapi is, or how it's different from
ldap://. And this search of the OpenLDAP documentation is sadly
Can you tell me which LDAP browsers do support this scheme? After all,
the other part of my message was asking for advice on which was best.
There are two ways you, the development team, can think about OpenLDAP:
A) "You have to prove your worthiness to use this software by having a
wide knowledge of Unix history, unwritten conventions, cryptic man-pages
and a perfect recall of command-line options. Searchable documentation
on the web - pah!"
B) "We want to lower barriers to entry and make it easier to use."
If the answer is B), then instead of telling me that I'm an idiot, you
might wish to reflect on what lessons can be learnt from my experience
to help other people in the future.
I must say that my experience with the OpenLDAP community thusfar has
not thrilled me with joy at the prospect of using the software for my
project. I speak as someone whose day job is nurturing, growing and
encouraging open source communities.