[Date Prev][Date Next]
Re: Missing documentation (ITS#1749)
> Here is 1st pass at the backend documentation patch:
> Feedback welcome. Mostly I've just manified existing text.
I'm applying it right now because something is better than nothing,
although I note there's something outdated in back-meta and in
the rewrite stuff (my fault, not yours, of course :)
I'll fix things later.
> The patch needs to be touched up, so I'll be updating it now and then.
> I present it now since you may be about to release 2.1.0beta. Please
> send me a note with the version number of the patch when it is applied.
> Then I'll switch to making a patch to the patch.
> Bug: Several EXAMPLE sections refer to files or directory trees with
> examples in the source. That's bad, I think these should be copied to
> ETCDIR/examples/. I can do that for Unix `Makefile.in's (with cp -r),
> but I don't know how to do it for Windows/Cygwin. (Or if it should be
> done at all. Are manual pages installed for Windows?)
No idea; I agree references to documents in source should disappear,
when these docs are turned in something more clean and standard (e.g.
extra manpages or a sort of white book on OpenLDAP).
> I'm writing a cursory slapd-ldap(5) manpage, but I need to know:
> What is binddn and bindpw used for? I know they are for "groups",
> but I don't know what that means - except it has something to do
> with ACLs.
It's a dn/cred that's used by back_group/back_attribute functions
when they search the target DS to check access (e.g. group/entry
lookup to find out if one is member of a group). So it's the creds
of some entry on the target directory taht is supposedly able to
access such info.
Dr. Pierangelo Masarati | voice: +39 02 2399 8309
Dip. Ing. Aerospaziale | fax: +39 02 2399 8334
Politecnico di Milano |
via La Masa 34, 20156 Milano, Italy |