Bayesian shenanigans (i.e. problems)

[Peter Bates]

Hello all...

> mkettler at EVI-INC.COM 15/01/04 15:56:50 >>>
At 05:38 AM 1/15/2004, David Lee wrote:
>"Me, too!" (bayes_toks ~ 50MB, bayes_toks.new ~ 1.4GB).  Glad I'm not
>alone.
>Yes those sizes are unreasonable... It sounds like expiry is never
running
>on your system.

>Try running expiry manualy using sa-learn --force-expire and see if
it
>clears things up.

Well, I've done a --force-expire, and got:

-rw-r--r--    1 postfix  postfix       40M Jan 16 14:51 bayes_seen
-rw-------    1 postfix  postfix      123k Jan 16 14:51 bayes_journal
-rw-------    1 postfix  postfix      265M Jan 16 14:51 bayes_toks
-rw-------    1 postfix  postfix      2.7G Jan 16 13:08 bayes_toks.new
-rw-r--r--    1 postfix  postfix      4.8M Oct 15 09:22 old_bayes_seen
-rw-r--r--    1 postfix  postfix       22M Oct 15 09:22 old_bayes_toks

now... and my SA/MS is timing out once again, now I've re-enabled Bayes
with use_bayes...

I'm almost tempted to have a normal SA run without Bayes, and then use
MCP to reprocess the message again with Bayes (or vice versa)... the
fact that the Bayes is making it time out, and then effectively timing
out the rest of the stuff despite it probably being 'positive' in a lot
of cases is proving far from jolly...



--------------------------------------------------------------------------------------------------->
Peter Bates, Systems Support Officer, Network Support Team.
London School of Hygiene & Tropical Medicine.
Telephone:0207-958 8353 / Fax: 0207- 636 9838