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

Re: contextCSN

To: Howard Chu <hyc@symas.com>
Subject: Re: contextCSN
From: Guillaume Arteta <arteta22000@gmail.com>
Date: Mon, 16 Feb 2009 18:27:47 +0100
Cc: openldap-technical@openldap.org
In-reply-to: <49999DAD.7070505@symas.com>
References: <282b35b20901211451i50630421x3216aaaf7eab6dcf@mail.gmail.com> <282b35b20902130613l7acd765frfa627ba13e77682d@mail.gmail.com> <4995F6BD.8070606@symas.com> <282b35b20902160859p73e5ec60p4eb362a591567f23@mail.gmail.com> <49999DAD.7070505@symas.com>

That bug is fixed in 2.4.14, you should upgrade.

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

Ok.

Small question :)

Should we put syncprov-sessionlog in 1000 only with the mode refreshOnly? or also with refreshAndPersist (the one I use) ?

Merci.
-----------
Guillaume.

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

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

Prev by Date: Re: contextCSN
Next by Date: LDAP Group
Index(es):
- Chronological
- Thread