OCNS Consulting wrote:
>
> Ken:
>
> I finally determined the issue with BerkeleyDB. The SASL configure script
> looks for "/usr/include/db3" which is found and contains (as expected) bdb3
> headers. Of course I compile SASL against bdb4 which is specified by
> including
> the options ->
>
>
Ken:
I finally determined the issue with BerkeleyDB. The SASL configure script
looks for "/usr/include/db3" which is found and contains (as expected) bdb3
headers. Of course I compile SASL against bdb4 which is specified by
including
the options ->
--with-bdb-libdir=/usr/local/BerkeleyDB
Lawrence Greenfield wrote:
>
> No, these files are a necessary part of Berkeley db.
>
> You can do:
>
> cd /var/imap/db
> rm `db_archive`
>
> as often as you like to keep the size down (in general it'll only need
> to keep one or two files around). You can even do this from a cron
> job.
>
Jonas Jacobsson wrote:
>
> Hi all,
>
> I'm a rather new Linux user and I have just started up
> my own server. The machine is right now running Debian 2.2 (potato),
> Exim, courier-imap and imp 2.2.
>
> My question is if anyone else on this list is running
> IMP (pref. 3.0) with Cyrus 1.5.19
Hi all,
I'm a rather new Linux user and I have just started up
my own server. The machine is right now running Debian 2.2 (potato),
Exim, courier-imap and imp 2.2.
My question is if anyone else on this list is running
IMP (pref. 3.0) with Cyrus 1.5.19 or above?
My goal is to upgrade to the much
No, these files are a necessary part of Berkeley db.
You can do:
cd /var/imap/db
rm `db_archive`
as often as you like to keep the size down (in general it'll only need
to keep one or two files around). You can even do this from a cron
job.
We tend to average about 10 megs of logs every hour.
Hey,
Is it possbile to disable BDB logging (or whatever that is --
/var/imap/db/log.0x)? The system creates 10Mb files and under high
traffic it's 100-150 Mb/day
Sincerely,
Nick
---
This message contains no viruses.
Guaranteed by Kaspersky Anti-Virus.
www.antivirus.lv
