DBERROR db4: /var/lib/imap/db/__db.001: unable to initializeenvironment lock: Function not implemented

[Mobeen Azhar]

True Simon, db4 works fine for Cyrus-imapd if either of the two are true:

1)  You are running on an i686 architecture.  In this case Posix thread
support exists and db4 works.

2)  You are not running on an i686 architecture _and_ have manually built
db4 without posix threads.

You are correct Simon in that skiplist works fine for the recommended
backend databases.  I only saw problems when using skiplist for the
tls_cache database - which is not recommended anyways.

Also Simon you are correct that is is not all that bad, since even I
(relatively new when it comes to Linux) has gotten it to work :)  Of course
your good and hard work in maintaining the cyrus-imapd rpm made it possible
:)

Thanks again,

--Moby

They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety.  -- Benjamin Franklin

First they came for the Jews and I did not speak out because I was not a
Jew.
Then they came for the Communists and I did not speak out because I was not
a Communist.
Then they came for the trade unionists and I did not speak out because I was
not a trade unionist.
Then they came for me and there was no one left to speak out for me.  --
Pastor Martin Niemöller 

-----Original Message-----
From: simix at mailhub.ch.sauter-bc.com [mailto:simix at mailhub.ch.sauter-bc.com]
On Behalf Of Simon Matter
Sent: Monday, May 26, 2003 23:59
To: moby at mobsternet.com
Cc: info-cyrus at lists.andrew.cmu.edu
Subject: Re: DBERROR db4: /var/lib/imap/db/__db.001: unable to
initializeenvironment lock: Function not implemented


Mobeen Azhar schrieb:
> 
> The _only_ time I saw problems with skiplist was when using skiplist for
the
> tls_cache _and_ actually have TLS clients connect to the server.  Other
than
> that once scenario skiplist worked fine everywhere else.  You are using
> skiplist for tls_cache and have clients connect using TLS with no issues?
> If so, then it might just be a problem on RH 9.0 (which would not surprise
> me - RH 9.0 should never have been released!).

It's not all that bad! Sure, they have broken db4 but despite that, it
works fine for cyrus-imapd.
I don't think the skiplist problem is true. There are many users using
my cyrus-imapd rpms on RedHat 9 and they use it with skiplist without
any problem. Of course the rpms use skiplist only for the recommended
backends.

Simon

> 
> --Moby
> 
> They that can give up essential liberty to obtain a little temporary
safety
> deserve neither liberty nor safety.  -- Benjamin Franklin
> 
> First they came for the Jews and I did not speak out because I was not a
> Jew.
> Then they came for the Communists and I did not speak out because I was
not
> a Communist.
> Then they came for the trade unionists and I did not speak out because I
was
> not a trade unionist.
> Then they came for me and there was no one left to speak out for me.  --
> Pastor Martin Niemöller
> 
> -----Original Message-----
> From: owner-info-cyrus at lists.andrew.cmu.edu
> [mailto:owner-info-cyrus at lists.andrew.cmu.edu] On Behalf Of Patrick Morris
> Sent: Monday, May 26, 2003 10:39
> To: Amos Gouaux
> Cc: info-cyrus at lists.andrew.cmu.edu
> Subject: Re: DBERROR db4: /var/lib/imap/db/__db.001: unable to
> initializeenvironment lock: Function not implemented
> 
> Ditto here.  Solaris 9 with skiplist.  We had a hell of a time with
> db4.1 (we'd get corruption in our databases at least daily), but since
> migrating to skiplist a little over a month ago we've had absolutely no
> database problems at all.
> 
> Amos Gouaux wrote:
> 
> >We sure haven't had any problems with skiplist.  Though, we're
> >running on Solaris, not Linux.
> >
> >
> >