https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6120
--- Comment #6 from Theo Van Dinter <[email protected]> 2009-05-26 13:31:20 PST --- (In reply to comment #5) > Maybe the way that the expiry process is being run, is allowing it to time out > after 5 minutes. I mean, what if you spawned another thread or process or > something, and it ran out-of-band for as long as it needed to? Well, because that's not how SA works. ;) Third party folks are not going to want the modules spawning processes -- what if you're on a platform that doesn't have fork(), for example? So the general process is to act like the "spamassassin" script, and therefore single process, no spawning children, etc. fyi: there was actually talk about doing that w/ spamd, though it hasn't been implemented yet. I agree, you're probably seeing amavis doing a timeout which kills the process and leaves behind the temp DB files. There's really no good single way to deal with everyone's setup, so you need to configure appropriately for how you're doing things. In your case, yeah, I would disable the auto-expiry and then do the cronjob. Or, change the Bayes backend to something that expires faster, like SQL. Or both. :) -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
