http://bugzilla.spamassassin.org/show_bug.cgi?id=3224
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From [EMAIL PROTECTED] 2004-03-28 08:28 -------
the output you've shown is completely valid. bayes is looking at expiring
tokens, it finds it can't estimate expiry, so it has to sit there and go
through
your DB calculating which tokens it should get rid of. if you have a large DB,
slow CPU, or a small amount of RAM (causes thrashing), it could take a while.
from your debug output, the DB isn't large, so... as for corruption, the
expiry first pass doesn't change the DB at all, so there's no corruption.
however, if you are deleting the lock file while the expiry run is going, that
is going to cause corruption -- don't do that unless you're sure the process
which set the lock is no longer running. (which should never happen)
you can disable autoexpiry by setting "bayes_auto_expire 0". then you can run
"sa-learn --force-expire" whenever you want.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
