[Kolab-devel] IMAP4 locking

[Stephan Buys]

Here is a patch against the kolab imapd.spec, I can commit it if there are no
objections...

Index: imapd.spec
===================================================================
RCS file: /kolabrepository/server/imapd/imapd.spec,v
retrieving revision 1.16
diff -u -p -r1.16 imapd.spec
--- imapd.spec  15 Jul 2004 14:37:22 -0000      1.16
+++ imapd.spec  1 Sep 2004 14:23:20 -0000
@@ -45,6 +45,7 @@ Release:      20040706_kolab
 %option       with_drac     no
 %option       with_annotate no
 %option       with_ldap     no
+%option              with_skiplist yes

 #   list of sources
 Source0:      ftp://ftp.andrew.cmu.edu/pub/cyrus-mail/cyrus-imapd-%{version}.tar.gz
@@ -190,11 +191,16 @@ AutoReqProv:  no
         --with-statedir=%{l_prefix}/var/imapd \
         --with-auth=unix \
         --without-libwrap \
-        --with-perl \
         --without-ucdsnmp \
         --with-cyrus-prefix=%{l_prefix} \
         --with-cyrus-user=%{l_rusr} \
-        --with-cyrus-group=%{l_rgrp}
+        --with-cyrus-group=%{l_rgrp} \
+%if "%{with_skiplist}" == "yes"
+        --with-duplicate-db=skiplist \
+        --with-tls-db=skiplist \
+        --with-pts-db=skiplist \
+%endif
+        --with-perl

     #   redirect the hard-coded file paths
     %{l_shtool} subst \





On Wednesday 01 September 2004 08:00, Joon Radley wrote:
> Hi Martin,
> 
> I will describe the problem the way I was able to reproduce it. We have
> received many other variants on the same theme.
> 
> Note that under some conditions it happens and under other it works fine.
> This is why it took such a long time to diagnose.
> 
> When downloading a mailbox from the server for the first time the server
> will lock some objects and never free them, the server also does not return
> a body for the object but does return an OK status. With every subsequent
> synchronization the objects remains lock, even after reboot.
> 
> While trying to resolve this I found some references to db3 and db4 locking
> problems on the internet. Cyrus created their own database backend to
> resolve this. (skiplist)
> 
> It would be nice to offer users an alternative database backend especially
> where problems and a workaround exist. Secondly I wondered if anybody has
> worked with skiplist who can give us some feedback on how stable it is. ( I
> was only able to test it under lab conditions ).
> 
> Best regards
> 
> Joon Radley
> Radley Network Technologies CC
> Cell: +27 (0)83 368 8557
> Fax: +27 (0)12 998 4346
> E-mail: joon at radleys.co.za
>   
> 
> > -----Original Message-----
> > From: kolab-devel-bounces at kolab.org 
> > [mailto:kolab-devel-bounces at kolab.org] On Behalf Of Martin Konold
> > Sent: Tuesday, August 31, 2004 6:37 PM
> > To: Kolab development coordination
> > Subject: Re: [Kolab-devel] IMAP4 locking
> > 
> > Am Dienstag, 31. August 2004 17:38 schrieb Joon Radley:
> > 
> > Hi Joon,
> > 
> > > One of the biggest problems reported by users is the locking of 
> > > objects on the IMAP4 server. Has anybody ever had a look at the 
> > > "skiplist" backend option?
> > 
> > Can you please elaborate more into details what kind of 
> > problems users report?
> > 
> > Regards,
> > -- martin
> > 
> > Dipl.-Phys. Martin Konold
> > 
> > e r f r a k o n
> > Erlewein, Frank, Konold & Partner - Beratende Ingenieure und 
> > Physiker Nobelstrasse 15, 70569 Stuttgart, Germany
> > fon: 0711 67400963, fax: 0711 67400959
> > email: martin.konold at erfrakon.de
> > 
> > _______________________________________________
> > Kolab-devel mailing list
> > Kolab-devel at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-devel
> 
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
> 
> 
> 

-- 
Stephan  Buys
Code Fusion cc.
Tel: +27 11 391 1412
Mobile: +27 83 294 1876
Email: s.buys at codefusion.co.za

E-mail Solutions, Kolab Specialists.
http://www.codefusion.co.za