Jason Frisvold wrote: > Wow.. that sucked.. Finished message below.. My apologies for the > previous unfinished message. > > On 11/26/06, Jason Frisvold <[EMAIL PROTECTED]> wrote: >> On 11/25/06, Matt Kettler <[EMAIL PROTECTED]> wrote: >> > Bayes_toks should trim itself automatically. >> >> I understand that, but I was wondering if it's possible to halt that >> and do a manual expire at specific intervals so I can control the load >> on the system. Expiry seems to take a while... >> >> > Have you done a sa-learn --dump magic? How long has it been since >> expiry >> > ran on your system? How may tokens are in the DB? >> >> I use spamc/spamd so I think expiry is happening all the time, tho I'm >> not sure how to tell. > > I'm checking now how many tokens there are.. It's taking forever.. > If I get a result, I'll let you know... > >> > Try running sa-learn --force-expire. Does that run (probably for a >> long >> > time) and then fix the problem? > > I'll give this a shot and see what happens.. Does spamassassin have > to be halted to do this? No, you can leave SA running.. however, while it's running sa-learn will have the R/W lock on the bayes database, so no autolearning will happen unless you're using the bayes_learn_to_journal option. (normally only atime updates are journaled.)
> > > While we're looking at database usage.. Does the AWL expire? Nope. > There's > only 17 million rows in my AWL database... *grin* There doesn't seem > to be any sort of time related field by default, so adding one may > help? Yep.. at present the only way to "expire" it is to use check-whitelist --clean on the database file. This will purge all the "single hit" entries. This script comes in the "tools" subdir of the tarball, but isn't installed by default. It also only seems to work with db_file type AWL databases. No SQL support. IMHO, this limitation makes the AWL not-ready for primetime. I would not use it on anything but fairly small-scale systems (ie: less than 5k messages a day) until a reasonable expiry system is added.
