On Donnerstag, 11. Mai 2006 20:00 Matt Kettler wrote: > First, adding --sync is redundant. --force-expire implies --sync > because it would be foolish for SA to attempt expiry without syncing > first.
I found that in the documentation after I sent the mail. > Your expiry will take much longer. On server 1 with such a large > bayes DB it could take 10 minutes or more. > expired old bayes database entries in 118 seconds > 214732 entries kept, 1312 deleted > token frequency: 1-occurrence tokens: 2.50% > token frequency: less than 8 occurrences: 71.89% OK, because I still didn't reach my tokens limit, I never really had an expire running. > > On http://wiki.apache.org/spamassassin/BayesForceExpire is says you > > should stop SA before --force-expire, is that a must or a > > recommendation? > It's a recommendation. If SA is still running and is in the middle of > auto-learning, sa-learn will have to wait for it to finish before it > can lock the DB R/W. OK, learning is quick anyway, so no problem here. The expire will definitely run much longer, as you say. But what happens when SA wants to auto-learn another message while expire runs? Will it wait and timeout or just skip autolearning? Skipping would be no problem for me, but a timeout could be nasty. > It's in the manpage, under the description of the "score" keyword. > > --- > If four valid scores are listed, then the score that is used depends > on how SpamAssassin is being used. The first score is used when both > Bayes and network tests are disabled (score set 0). The second score > is used when Bayes is disabled, but network tests are enabled (score > set 1). The third score is used when Bayes is enabled and network > tests are disabled (score set 2). The fourth score is used when Bayes > is enabled and network tests are enabled (score set 3). --- Ah, it's simply the four different score numbers. If english would be my mother tongue, I could have guessed that probably. Thx. mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0660/4156531 .network.your.ideas. // PGP Key: "lynx -source http://zmi.at/zmi3.asc | gpg --import" // Fingerprint: 44A3 C1EC B71E C71A B4C2 9AA6 C818 847C 55CB A4EE // Keyserver: www.keyserver.net Key-ID: 0x55CBA4EE
pgpwsG66adXtb.pgp
Description: PGP signature
