[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: one slapd to multiple ldbm's



At 08:59 AM 10/2/00 -0700, Mark Whitehouse wrote:

>>You need to provide the glue... named referral objects in
>>superior context referring to the root of the subordinate
>>context.
>>
>>Then when the client searches the superior context, the
>>server will return a referral for each referral object
>>within scope.
>
>OK, that makes sense.  However I have run into another problem.
>
>Assume I have multiple namingContexts on one server i.e.
>
>  database ldbm
>  suffix "ou=people,dc=foo,dc=com"
>  directory /var/ldbm/foo-people
>  index objectclass eq
>
>  database ldbm
>  suffix "ou=devices,dc=foo,dc=com"
>  directory /var/ldbm/foo-devices
>  index objectclass eq
>
>  database ldbm
>  suffix "dc=foo,dc=com"
>  directory /var/ldbm/foo
>  index objectclass eq
>
>How do I create the referrals in the third namingContext, which refer the
>entries in the first and second.  I need to be able to add the following
>referral entries to the third naming context:
>
>  dn: ou=devices,dc=foo,dc=com
>  ou: devices
>  ref: ldap://localhost/ou=devices,dc=foo,dc=com
>  objectclass: referral
>  objectclass: extensibleObject
>
>  dn: ou=people,dc=foo,dc=com
>  ou: devices
>  ref: ldap://localhost/ou=people,dc=foo,dc=com
>  objectclass: referral
>  objectclass: extensibleObject
>
>However, as far as I can see there is no way to specify a namingContext to
>use when performing an ldapadd operation.

The easiest way to do this is to bring up slapd with only the
one suffix "dc=foo,dc=com", add the two referral objects,
and then restart the server with the full configuration.

This really should be handled by our ManageDsaIT code, but
isn't (yet).