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

Re: Design for large openldap deployments

To: openldap-technical@openldap.org
Subject: Re: Design for large openldap deployments
From: Dieter KlÃnter <dieter@dkluenter.de>
Date: Sat, 14 Dec 2013 18:50:29 +0100
In-reply-to: <alpine.BSF.2.00.1312141130220.59400@pohjola.cksoft.de>
Organization: AVCI
References: <alpine.BSF.2.00.1312131812040.59400@pohjola.cksoft.de> <20131213222202.7b0091be@pink.avci.de> <alpine.BSF.2.00.1312141130220.59400@pohjola.cksoft.de>

Am Sat, 14 Dec 2013 11:31:09 +0100 (CET)
schrieb Christian Kratzer <ck-lists@cksoft.de>:

> Hi,
> 
> On Fri, 13 Dec 2013, Dieter KlÃnter wrote:
> > Michael is quite correct in his comments regarding slapo_policy,
> > but in priciple i have realised this design in a cascading
> > directory with more than 100 slaves.
> 
> read only slaves or slaves with full write access ?
> 
> The latter is the thing I need and the thing I am concerned about.

read, and write operations by chaining.

-Dieter


-- 
Dieter KlÃnter | Systemberatung
http://dkluenter.de
GPG Key ID:DA147B05
53Â37'09,95"N
10Â08'02,42"E

Follow-Ups:
- Re: Design for large openldap deployments
  - From: Christian Kratzer <ck-lists@cksoft.de>

References:
- Design for large openldap deployments
  - From: Christian Kratzer <ck-lists@cksoft.de>
- Re: Design for large openldap deployments
  - From: Dieter Klünter <dieter@dkluenter.de>
- Re: Design for large openldap deployments
  - From: Christian Kratzer <ck-lists@cksoft.de>

Prev by Date: Re: ldapsearch limit of 500 entries
Next by Date: Re: Design for large openldap deployments
Index(es):
- Chronological
- Thread