The issue is that bayes expiry is broken under some circumstances as evidenced by this listing of my bayes database area, possibly because its taking more than 10 minutes, or possibly because there is a bug in the code
-rw------- 1 defang defang 32 Jan 26 12:19 bayes.lock -rw------- 1 defang defang 2750039 Jan 26 12:27 bayes_journal -rw------- 1 defang defang 20897792 Jan 26 12:19 bayes_seen -rw------- 1 defang defang 21733376 Jan 26 12:22 bayes_toks -rw------- 1 defang defang 9437184 Jan 26 12:22 bayes_toks.expire16781 -rw------- 1 defang defang 11173888 Jan 26 11:35 bayes_toks.expire23012 -rw------- 1 defang defang 5341184 Jan 26 10:54 bayes_toks.expire27549 -rw------- 1 defang defang 11182080 Jan 26 11:59 bayes_toks.expire27570 -rw------- 1 defang defang 11403264 Jan 26 10:44 bayes_toks.expire4752 I had thought that you would want to know about it. What I want is to allow expiry to happen opportunistically without having to set "bayes_auto_expire 0" and run an "sa-learn --force-expire" every hour, but that does not appear to be possible. That being the case perhaps a note in the documentation would do the trick. Something to warn people that on high volume sites they cannot afford to allow bayes to run in its default mode of operation. - rick On Tue, 27 Jan 2004, Theo Van Dinter wrote: > On Tue, Jan 27, 2004 at 03:57:56PM +0000, David Lee wrote: > > The MailScanner maintainer, Julian Field, is very responsive, and he has > > already coded up an alternative way of driving SA from MS, so that its use > > of SA can avoid auto-expire (and thereby avoid the possible multiple > > simultaneous expires) and instead do a more controlled, occasional and > > explicit expire. > > Which is different from disabling auto_expire ("bayes_auto_expire 0") > in the config and running "sa-learn --force-expire" when you want? > > The code already tries to avoid multiple parallel expire runs BTW. > First, the DB is locked, second, the running expire updates a specific > magic token in the DB which tells any other instance that an expire is > occuring and they should abort. > > So what's the issue? > > -- > Randomly Generated Tagline: > Who wants to remember that escape-x-alt-control-left shift-b puts you into > super-edit-debug-compile mode? > (Discussion in comp.os.linux.misc on the intuitiveness of commands, especially > Emacs.) > ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk