Re: (ITS#6277) Missing documentation for cn=config

[ryans@aweber.com]

Gavin,

> Well there are two places that talk about how to convert from slapd.conf
> to cn=config formats. In the guide and man pages, so that is the best
> way to do a full conversion and see the end result.
>
> Where would you like to see these added?
>
> Thanks for the feedback as always!

My vote would be section 5.2.2.3 of the Admin Guide.  Currently, it has 2 examples of loading modules consisting of
libtool libraries, but I would think that it would be good to give an example which, for pedagogical purposes, explained
how to instantiate an overlay in cn=config.  For example, ppolicy and autogroup:

   dn: olcOverlay=ppolicy,olcDatabase={1}hdb,cn=config
   objectClass: olcOverlayConfig
   objectClass: olcPPolicyConfig
   olcOverlay: ppolicy

   dn: olcOverlay=autogroup,olcDatabase={1}hdb,cn=config
   objectClass: olcOverlayConfig
   objectClass: olcAutomaticGroups
   olcOverlay: autogroup
   olcAGattrSet: groupOfNames labeledURI member

Perhaps it would also be good to emphasize the need for overlay-specific objectclasses, such as the aforementioned
'olcOverlayConfig' and 'olcPPolicyConfig'.  It probably also wouldn't hurt to mention that there are certain
overlay-specific attributes, i.e. olcAGattrSet, that are necessary to make full use of the module, and that grepping
through the contrib module's source can help one identify said attributes' names in lieu of adequate documentation.
Something like: grep -C3 NAME contrib/slapd-modules/autogroup/autogroup.c, maybe?


Thanks as always,
Ryan