Hi,
I've followed this thread with plenty of interest, because we've had the
same problem for quiet some time. Since we have upgraded from FC? to
RHAS3 a year ago.
As recommended by You, we switched to the skiplist format, one weak ago.
You asked to be informed of the changes. Here they are:
Hi,
I've followed this thread with plenty of interest, because we've had the
same problem for quiet some time. Since we have upgraded from FC? to
RHAS3 a year ago.
As recommended by You, we switched to the skiplist format, one weak ago.
You asked to be informed of the changes. Here they
On Fri, 2005-09-16 at 19:01 +0200, Simon Matter wrote:
Hi,
Thank you for the feedback, it's important for me to hear how it works for
others. Is this a large server where you had the BerkeleyDB problems?
Simon
The server I wrote about is a small one. Here's the details.
# cat
As the originator of the thread, I should report. We have been
running without a problem for four days with the change. It
is a medium sized server with about 500 active accounts but around
2GB of traffic per day. It is a dual Xeon 3.0GHz EM64T with 4GB ram
running CentOS 4.1 x86_64
--
Well, I tried this and aborted the conversion. The cvt_cyrusdb ran for 10
minutes by which time my 10MB deliver.db file had become a 1GB
deliver.db.skiplist file.
So I simply moved the current deliver.db and tls_sessions.db aside,
configured imapd.conf for skiplist on them, and then started
On Thu, 8 Sep 2005, Simon Matter wrote:
One special note:
The cyrus-imapd package you are using (the package from RHEL4 is based on
my Invoca package) tries to convert the db files automatically on startup.
However, the version you have has a bug which prevents it from converting
all db files
On Thu, 8 Sep 2005, Simon Matter wrote:
One special note:
The cyrus-imapd package you are using (the package from RHEL4 is based
on
my Invoca package) tries to convert the db files automatically on
startup.
However, the version you have has a bug which prevents it from
converting
all db
We are having constant problems with cyrus locking up and filling
up the system log with gigabytes of errors like this:
Sep 8 13:07:09 mail master[23769]: process 21100 exited, status 75
Sep 8 13:07:09 mail master[23769]: service imaps pid 21100 in READY state:
terminated abnormally
Sep 8
On Thu, 8 Sep 2005, Simon Matter wrote:
You may want to switch berkeley dbs to skiplist to try how it goes.
By default only duplicate_db and tlscache_db are berkeley so you may try
this in /etc/imapd.conf:
duplicate_db: skiplist
tlscache_db: skiplist
Will this change what is used for the
We are having constant problems with cyrus locking up and filling
up the system log with gigabytes of errors like this:
Sep 8 13:07:09 mail master[23769]: process 21100 exited, status 75
Sep 8 13:07:09 mail master[23769]: service imaps pid 21100 in READY
state:
terminated abnormally
Sep
On Thu, 8 Sep 2005, Simon Matter wrote:
You may want to switch berkeley dbs to skiplist to try how it goes.
By default only duplicate_db and tlscache_db are berkeley so you may try
this in /etc/imapd.conf:
duplicate_db: skiplist
tlscache_db: skiplist
Will this change what is used for the
Okay, thanks. I will try this next time I can take things down
On Thu, 8 Sep 2005, Simon Matter wrote:
On Thu, 8 Sep 2005, Simon Matter wrote:
You may want to switch berkeley dbs to skiplist to try how it goes.
By default only duplicate_db and tlscache_db are berkeley so you may try
this in
12 matches
Mail list logo
