deliver.db and related issues
Rob Siemborski
rjs3 at andrew.cmu.edu
Wed Oct 15 14:19:34 EDT 2003
On Wed, 15 Oct 2003, Ben Carter wrote:
> >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 would not unilaterally stop running ctl_cyrusdb, especially since
semantics of it may change in later versions.
> 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.
Cyrus 2.2 can be compiled without Berkeley DB support at all.
-Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
Research Systems Programmer * /usr/contributed Gatekeeper
More information about the Info-cyrus
mailing list