RE: monitor schema

["Howard Chu" <hyc@highlandsun.com>]

> Of course the objectClass and attributeType definitions
> should be hardcoded into schema_prep.c;

I would prefer that we break out the code for registering attributes and
objectclasses in schema_prep.c into callable functions (like register_syntax)
and just have back-monitor register its schema when it initializes. Unless
there's specific front-end dependencies on knowing these things in advance...
?

> I'll start adding
> some stuff, protected behind #ifdef MONITOR_DEVEL, leaving
> the OIDs blank.  After I commit it, if you find it reasonable
> you may start assigning experimental OIDs, so that it becomes
> at least testable.  Fixing the existing code should be
> trivial, and adding new levels should not be that hard.



  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support