Re: (ITS#5576) Missing attribute type 'managedInfo' referenced with SUP

[hyc@symas.com]

h.b.furuseth@usit.uio.no wrote:
> ando@sys-net.it writes:
>> I suspect something like: if back-monitor and/or back-ldap are built as
>> modules, and loaded in the wrong order (back-ldap first, back_monitor
>> then), 'olmDbURIList' is likely to be registered __before__
>> 'managedInfo'.
>
> So, a manpage fix something like this?
>
>    If monitor is a dynamically loaded module, it should be "moduleload"ed
>    before any modules it wants to monitor.  A dynamically loaded monitor
>    may be unable to monitor a statically built module.

Not necessary. The order of moduleloads is irrelevant.

back-monitor initializes its schema as soon as the module is loaded. All of 
the other backends initialize their monitor schema when a backend is first 
instantiated. The problem you're talking about here doesn't exist.
-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/