Forum Replies Created
-
Posts
-
Seems that if you want custom schemas you have to let openldap do the conversion to the new model. To the point, set up your custom schema file as you would have done previously (include statement in slapd.conf and the schema file under schema directory). Then stop slapd and trash (or stash) the old slapd.d directory and create a new slapd.d (check that the permissions are the same on) directory. After that you just type
#> slaptest -f slapd.conf -F slapd.d
and boom, you have slapd.d hierarchy that has your custom schemas. Now just start slapd again and start adding yuor attributes.
jokke
Well it seems that there’s some trickery how to correctly format the slapd configuration files when they follow the new LDAP enabled config model. And if you have both, the new way to store configs and the old single file way, the new way takes precedence and what ever you store to slapd.conf file doesn’t get read at startup nor are the schema files at schema directory read. By naming the slapd.d directory at /etc/openldap/ to something else, the old config files (and schema files) get read so if you’ve had your custom schemas there on tiger server this way you can restore that behavior.
On the other hand the new way to store configs and have the changes to be read at runtime is quite nice, so I’ll try to figure out how to do correctly custom schemas with that and post results here in case anybody stumbles to this thread at later day.
jokke
