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

Re: contextCSN

To: jakjr <joao.alfredo@gmail.com>
Subject: Re: contextCSN
From: Howard Chu <hyc@symas.com>
Date: Thu, 22 Jan 2009 07:46:43 -0800
Cc: Guillaume Arteta <arteta22000@gmail.com>, openldap-technical@openldap.org
In-reply-to: <eca827cf0901220627t5e16a881r4825d3d914a7cbd5@mail.gmail.com>
References: <282b35b20901211451i50630421x3216aaaf7eab6dcf@mail.gmail.com> <eca827cf0901220627t5e16a881r4825d3d914a7cbd5@mail.gmail.com>
User-agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.9.1b3pre) Gecko/20090115 SeaMonkey/2.0a1pre Firefox/3.0.3

jakjr wrote:

I dont thing so.

I have found some situations where the contextCSN is the same, but the
tree are not synced.

Then you have found a bug that should be reported to the ITS. Two servers with same contextCSN are supposed to have matching content.

--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/

Follow-Ups:
- Re: contextCSN
  - From: jakjr <joao.alfredo@gmail.com>

References:
- Re: contextCSN
  - From: Guillaume Arteta <arteta22000@gmail.com>
- Re: contextCSN
  - From: jakjr <joao.alfredo@gmail.com>

Prev by Date: ldap_simple_bind_s fails intermittently, when run in an loop
Next by Date: Re: contextCSN
Index(es):
- Chronological
- Thread