bayes expire tokens

[Brady Tucker]

 Peter... You are correct.. Before I got this under control my bayes_seen
was indeed growing at an insane pace... Upwards of 100 to 300  megs after a
week of fighting it and just running a job to delete the lock files and
ignore the problem for far too long :)

Now all the boxes have stabilized around 20 megs for toks and 22 megs for
seen... Seems to be the average on all of them anyway... Other boxes I
manage for clients seem to run around 3 and 5 megs for each db respectively
on lower volume machines.

I haven't started fresh with my db's in a long long time... Don't seem to
have, or haven't noticed a bayes poisoning issues, so I've had no reason to.
Perhaps because of the # of msgs I get a day they are nullified ?  But Back
when this was a problem I routinely replaced the db with the starter db
provided by somebody here (thanks).  We also have a common imap box that is
replicated amongst the servers and learned with Julians's script hourly on
each box... And all the techs and a few people I trust are very good about
training.. So perhaps that helps that issue as well.

                                                 Brady A. Tucker
                                                 batucker at icnet.net
                                                 Internet Complete!
                                                 w w w . i c n e t . n e t



-----Original Message-----
From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK] On Behalf
Of Peter Bonivart
Sent: Tuesday, March 08, 2005 7:00 PM
To: MAILSCANNER at JISCMAIL.AC.UK
Subject: Re: bayes expire tokens

Brady Tucker wrote:
> Here's what finally fixed it for me... I run the bayes expire script from
a
> cron job at least 3 times a day.  If I Run it twice and I get a few lock
> files... Run it once/day and I get a crapload.... Run it three times/day
and
> its smooth.   I therefore do it every 8 hours.  I'm assuming that the
bayes
> DB gets so big that doing the expire job only once/day it takes to long to
> finish and it gives up and tries again repeatedly ?  (even when running in
> tmpfs)????  I don't know why.. But it works.. And worked on all 4
servers...
> The expiry only takes about 1-3 minutes when run 3 times a day... Was
taking
> upwards of 7 to 10 when once/day... Can't believe it was the problem...
> But.. There you have it.  Somebody smarter than me can either tell me I'm
> crazy... Or explain why.

You may be on to something there. I output the expire run to a file and
check it from time to time and it never takes more than a minute to
finish, big difference from your 7-8. I remember setting one of my
servers to twice a day since it took more than a minute on that one.

Another thing, when you run the same Bayes DB for a long time the
bayes_seen gets insanely large, the expire doesn't touch it or..?

--
/Peter Bonivart

--Unix lovers do it in the Sun

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ (http://www.mailscanner.biz/maq/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ (http://www.mailscanner.biz/maq/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!