statuscache and fatal
brong at fastmail.fm
Wed Nov 4 07:39:20 EST 2009
On Wed, Nov 04, 2009 at 11:30:20AM +0100, Cyril Servant wrote:
> I wonder why is a "fatal" function called when the statuscache backend
> can't be opened. This makes the process terminate (then fork again,
> then terminate, then...). This is not logical, because statuscache
> is... a cache ! Cyrus should work fine without (and actually, it does,
> with the patch attached).
> As we use an sql backend for statuscache, when the sql server is not
> available, we prefer that cyrus-imapd works without cache than a total
You have a good point :) I've committed a patch for it to CVS. I also
protected the rest of the functions by not setting statuscache_dbopen
and by testing for it at the start of each entry point.
More information about the Cyrus-devel