>
>
>Oh, and using BerkeleyDB for deliver and tls stuff seems to be
>fine. The number of lockers will climb during peak periods, but
>then taper back down when traffic subsides. It just seems like
>mailboxes.db was an application not terribly well suited for it.
>
We got deadlocks using BDB for
> On Wed, 3 Apr 2002 22:19:02 +0300,
> Nick Ustinov <[EMAIL PROTECTED]> (nu) writes:
nu> We are planning to switch production server from 2.0.16 to 2.1.3/skiplist.
nu> The system has about 60 mailboxes and is quite heavily loaded (seeing
nu> alot of db lockers). Are there any hidden c
Nick Ustinov schrieb:
>
> We are planning to switch production server from 2.0.16 to 2.1.3/skiplist.
> The system has about 60 mailboxes and is quite heavily loaded (seeing
> alot of db lockers). Are there any hidden catches people i should avoid?
> Besides converting mailboxes file using cvt
We are planning to switch production server from 2.0.16 to 2.1.3/skiplist.
The system has about 60 mailboxes and is quite heavily loaded (seeing
alot of db lockers). Are there any hidden catches people i should avoid?
Besides converting mailboxes file using cvt_cyrusdb is there anything else I
