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

Re: Design for large openldap deployments

To: Dieter KlÃnter <dieter@dkluenter.de>
Subject: Re: Design for large openldap deployments
From: Christian Kratzer <ck-lists@cksoft.de>
Date: Sat, 14 Dec 2013 11:31:09 +0100 (CET)
Cc: openldap-technical@openldap.org
In-reply-to: <20131213222202.7b0091be@pink.avci.de>
References: <alpine.BSF.2.00.1312131812040.59400@pohjola.cksoft.de> <20131213222202.7b0091be@pink.avci.de>
User-agent: Alpine 2.00 (BSF 1167 2008-08-23)

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.

Greetings
Christian

--
Christian Kratzer                      CK Software GmbH
Email:   ck@cksoft.de                  Wildberger Weg 24/2
Phone:   +49 7032 893 997 - 0          D-71126 Gaeufelden
Fax:     +49 7032 893 997 - 9          HRB 245288, Amtsgericht Stuttgart
Web:     http://www.cksoft.de/         Geschaeftsfuehrer: Christian Kratzer

Follow-Ups:
- Re: Design for large openldap deployments
  - From: Dieter KlÃnter <dieter@dkluenter.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>

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