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

Re: contextCSN

To: Howard Chu <hyc@symas.com>
Subject: Re: contextCSN
From: jakjr <joao.alfredo@gmail.com>
Date: Thu, 22 Jan 2009 14:10:10 -0200
Cc: Guillaume Arteta <arteta22000@gmail.com>, openldap-technical@openldap.org
In-reply-to: <497894E3.4040305@symas.com>
References: <282b35b20901211451i50630421x3216aaaf7eab6dcf@mail.gmail.com> <eca827cf0901220627t5e16a881r4825d3d914a7cbd5@mail.gmail.com> <497894E3.4040305@symas.com>

ITS 5843, the delete bug.
http://www.openldap.org/its/index.cgi/Software%20Bugs?id=5843;selectid=5843

On Thu, Jan 22, 2009 at 1:46 PM, Howard Chu <hyc@symas.com> wrote:

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/

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

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