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?
> Do you call SA through MailScanner or amavis which might be interfering > with expire runs by timing out and killing SA? (This only matters for > tools that use the API.. Or technically a tool that uses the > spamassassin command line script, but no decent integration tools that > monitor execution time do that. Anything that calls spamc to access > spamd won't be able to kill off the expire process by killing spamc.)
Spamassassin is called via simscan which does not, to my knowledge, halt the process at any point. In addition, it uses spamc/spamd so by your explanation, even if it did, it wouldn't affect the expiry process. While we're looking at database usage.. Does the AWL expire? 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?
-- Jason 'XenoPhage' Frisvold [EMAIL PROTECTED]
-- Jason 'XenoPhage' Frisvold [EMAIL PROTECTED]
