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

Re: replication issue

To: John Morrissey <jwm@horde.net>
Subject: Re: replication issue
From: Aaron Richton <richton@nbcs.rutgers.edu>
Date: Wed, 19 Nov 2008 18:09:49 -0500 (EST)
Cc: openldap-software@openldap.org
In-reply-to: <20081119202750.GA15392@boost.horde.net>
References: <49233042.3000109@higis.ru> <87fxlnwk1u.fsf@rubin.l4b.de> <20081119202750.GA15392@boost.horde.net>

On Wed, 19 Nov 2008, John Morrissey wrote:

For client operations, doesn't syncrepl operate as the rootdn, which is
exempt from size/time limitations?

Internally, syncrepl acts as the rootdn. However, when going over the wire to the provider, it must be configured with a binddn and credentials. Certainly there is nothing in the client stopping you from specifying the rootdn as the syncrepl binddn, but that is not considered best practice.

I'm trying the latest RE24 on the client today.


Probably well advised...please let the list know how it goes...

Follow-Ups:
- Re: replication issue
  - From: John Morrissey <jwm@horde.net>

References:
- replication issue
  - From: Dmitriy Kirhlarov <dimma@higis.ru>
- Re: replication issue
  - From: "Dieter Kluenter" <dieter@dkluenter.de>
- Re: replication issue
  - From: John Morrissey <jwm@horde.net>

Prev by Date: RE: replication issue
Next by Date: Re: replication issue
Index(es):
- Chronological
- Thread