deliver.db and related issues

Ben Carter cecropia+ at pitt.edu
Wed Oct 15 14:08:44 EDT 2003


Rob Siemborski wrote:

>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.
>  
>
OK.

>  
>
>>(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.
>
We're thinking of having a cron job that locks the mailboxes file (flat file) and just copies
it to a different disk occasionally.  So, I'm assuming in this case that I wouldn't
need recovery using ctl_cyrusdb at all, since we don't care about the
deliver.db file's recovery.  Am I correct?

I'm not trying to re-invent the wheel, but just trying to simplify the Cyrus
part of our server's configuration.  I don't like ctl_cyrusdb calling BDB
routines at all (especially since we have no BDB files) because if it gets hung
or spews error messages to syslog, both of which it's done to us, we'd rather
just avoid it.  If there is a way to get ctl_cyrusdb to just backup the flat
mailboxes file and do its noop for the skiplist deliver.db that would be fine
with us too.

>
>  
>
>>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?
>  
>
We did, but I wiped out db/*, db.backup1/* and db.backup2/* and these files
reappeared - I assume they were created by ctl_cyrusdb.

Thanks,

Ben

Ben Carter
University of Pittsburgh
bhc at pitt.edu
412-624-6470







More information about the Info-cyrus mailing list