Gerd Schering wrote:
Pierangelo Masarati wrote:
Dynlist does not allow massaging, so an option would be to stack a rwm before dynlist, so that rwm can massage the attribute names from persID to memberID before gathering. Looks ugly.
Even if I will look for another solution (as promised in my previous posting), I am somewhat curious: where can I find an example dealing with overlay stacking?
Please keep replies on the list. Overlay stacking is trivial: just configure more than one. From slapd.conf(5):
overlay <overlay-name> Add the specified overlay to this database. An overlay is a piece of code that intercepts database operations in order to extend or change them. Overlays are pushed onto a stack over the database, and so they will execute in the reverse of the order in which they were configured and the database itself will receive control last of all. See the slapd.overlays(5) manual page for an overview of the available overlays. Note that all of the database’s regular settings should be configured before any overlay settings.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati@sys-net.it ---------------------------------------
openldap-technical@openldap.org