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

Re: Slapd-meta stop at the first unreachable candidate

To: Michel Gruau <michel.gruau@laposte.net>
Subject: Re: Slapd-meta stop at the first unreachable candidate
From: Marc Patermann <hans.moser@ofd-z.niedersachsen.de>
Date: Mon, 5 Sep 2011 17:41:22 +0200
Cc: openldap-technical openldap org <openldap-technical@openldap.org>
In-reply-to: <25529317.86395.1313752439182.JavaMail.www@wwinf8218>
References: <25529317.86395.1313752439182.JavaMail.www@wwinf8218>
User-agent: Thunderbird 2.0.0.18 (Windows/20081105)

Michel,

Michel Gruau schrieb am 19.08.2011 13:13 Uhr:

It have a slapd-meta configuration as follows:

database meta
suffix dc=com
uri ldap://server1:389/dc=suffix1,dc=com
uri ldap://server2:389/dc=suffix2,dc=com
uri ldap://server3:389/dc=suffix3,dc=com

so while the 3 server serve different content (different suffixes), whydon't you split this into 3 databases? Have you tried this?


database meta
suffix dc=suffix1,dc=com
uri ldap://server1:389/dc=suffix1,dc=com

database meta
suffix dc=suffix2,dc=com
uri ldap://server2:389/dc=suffix2,dc=com

database meta
suffix dc=suffix3,dc=com
uri ldap://server3:389/dc=suffix3,dc=com


Marc

Follow-Ups:
- Re: Slapd-meta stop at the first unreachable candidate
  - From: Michel Gruau <michel.gruau@laposte.net>

Prev by Date: Re:Slapd-meta stop at the first unreachable candidate
Next by Date: Re: Slapd-meta stop at the first unreachable candidate
Index(es):
- Chronological
- Thread