--On Tuesday, September 09, 2008 8:59 PM +0200 Pierangelo Masarati ando@sys-net.it wrote:

...

I'll give what you suggested a try, but this is still a serious bug.

There's something I don't clearly get. As far as I understand, you are saying that consumers lose sync when the log database is purged before they have a chance to sync (because they were down). I don't see how they could sync, then. Of course, there should be a means for slapo-syncprov(5) to tell that, and force a refresh.

Because the consumer is supposed to do a full refresh if they find their context CSN doesn't match the contextCSN of the master.

See ITS#5376, ITS#5378, ITS#5465, ITS#5493, ITS#5282

--Quanah

--

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