On Thu, May 29, 2003 at 02:36:24PM -0500, Stewart, John wrote:
> I think you'll know my next question... when is it due? =)
Hopefully, in around a month. (more specifically, sometime around the
beginning of July is the plan.)
--
Randomly Generated Tagline:
Don't Hit A Man When He's Down. Kick
> > Perhaps it would be simpler for us SA admins to have a separate
> > setting to just turn off opportunistic auto-expiry, than having
> > to tinker with two config files. The 'sa-learn --force-expire'
> > could still benefit from the max_db_size setting in the standard
> > config file.
> >
> >
Mark Martinec said:
> Perhaps it would be simpler for us SA admins to have a separate
> setting to just turn off opportunistic auto-expiry, than having
> to tinker with two config files. The 'sa-learn --force-expire'
> could still benefit from the max_db_size setting in the standard
> config file
| BTW, good news for large site-wide bayes dbs: Theo has implemented a way
| to avoid auto-expiry in 2.60. The plan is that expiry can be disabled by
| setting bayes_expiry_max_db_size to 0.
|
| Then folks who wish to do an expiry from cron, can control this by using
| a config file which uses e
BTW, good news for large site-wide bayes dbs: Theo has implemented a way
to avoid auto-expiry in 2.60. The plan is that expiry can be disabled by
setting bayes_expiry_max_db_size to 0.
Then folks who wish to do an expiry from cron, can control this by using
a config file which uses e.g. "bayes_
