bayes expire tokens

Peter Bonivart peter at UCGBOOK.COM
Wed Mar 9 08:33:36 GMT 2005

    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

Brady Tucker wrote:
>  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.

But I meant that even though the expire run is successful I think that
the bayes_seen file is growing too large. Is it reasonable to have a
bayes_toks file of 5 MB and a bayes_seen file of 82 MB? The below is
from a system that has not been running for that long, these are the
only files, no expire files and it works well. I have seen bayes_seen
files with 300-500 MB, does it have to dig through it every time?

-rw-------   1 root     other       3462 Mar  9 09:26 bayes.mutex
-rw-------   1 root     other      95256 Mar  9 09:26 bayes_journal
-rw-------   1 root     other    82214912 Mar  9 09:26 bayes_seen
-rw-------   1 root     other    5308416 Mar  9 09:26 bayes_toks

/Peter Bonivart

--Unix lovers do it in the Sun

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ ( and
the archives (

Support MailScanner development - buy the book off the website!

More information about the MailScanner mailing list