On Tue, May 08, 2007 at 08:42:24PM +0200, Pierangelo Masarati wrote:

ahasenack@terra.com.br wrote:

...

The monitor backend attributes and object classes, when loaded, should also be exported in the subschema entries at the server.

I know of one ldap client that breaks because of this: luma. It says it can't display the cn=monitor entries because it doesn't know the object classes or attributes. I guess it uses this info to determine how to show each entry.

The schema is not exposed since it's considered experimental. To expose it, you need to #define LDAP_DEVEL.

It doesn't see a good idea for me to define LDAP_DEVEL just to get this schema published: probably many other things in openldap would change.