deliver.db and related issues

[Rob Siemborski]

On Wed, 15 Oct 2003, Ben Carter wrote:

> First of all we have duplicate delivery suppression turned off.
> However, deliver.db still seems to be maintained.  I saw a post about
> it being needed for sieve too but we don't plan to use sieve either.  My
> question is, can I totally disable the use of deliver.db
> without making code changes?

No.

> (For now, we changed deliver.db to skiplist since BDB format was causing
> hung and 'signaled to death by 10/11' lmtpd processes)
>
> Also, can the periodic execution of "ctl_cyrusdb -c" be safely disabled
> if one used a cron entry to make copies of the mailboxes file etc?

You probably still want to checkpoint, since otherwise recovery will take
much longer.  Note that this is more or less a noop for skiplist.

> Finally, since we have no Berkely DB files, what are all the __db...
> files that get created in the 'db' subdirectory and why is one of
> them 2MB in size?  Our test mailboxes file is only 72 bytes...

Those are Berkeley DB log files.

Did you have a berkeley db setup at one time?

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
Research Systems Programmer * /usr/contributed Gatekeeper