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

Re: syncrepl (refreshAndPersist) fails after system date is moved backwards

To: jan.cedergren@nsn.com, openldap-bugs@openldap.org
Subject: Re: syncrepl (refreshAndPersist) fails after system date is moved backwards
From: Quanah Gibson-Mount <quanah@zimbra.com>
Date: Tue, 04 Dec 2007 09:08:53 -0800
Content-disposition: inline
In-reply-to: <C229CE4D4774524B9FBAE66B18B0441804C033F4@esebe103.NOE.Nokia.com>
References: <C229CE4D4774524B9FBAE66B18B0441804C033F4@esebe103.NOE.Nokia.com>

--On December 4, 2007 12:24:09 PM +0200 jan.cedergren@nsn.com wrote:

Hello,


Software usage questions should be sent to openldap-software@openldap.org.

And no, I would not call this a bug. Since the replication mechanism depends specifically on time stamps, screwing with your system clock is a great way to screw up replication. ;)

--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration

Follow-Ups:
- RE: syncrepl (refreshAndPersist) fails after system date is moved backwards
  - From: <jan.cedergren@nsn.com>

References:
- syncrepl (refreshAndPersist) fails after system date is moved backwards
  - From: <jan.cedergren@nsn.com>

Prev by Date: Re: Problem to connect Ã LDAP server
Next by Date: (ITS#5259) SIGSEGV in slap_auxprop_store during SASL/OTP bind
Index(es):
- Chronological
- Thread