On Fri, 4 Sep 2015 11:08:35 -0700 Chris Cappuccio <ch...@nmedia.net> wrote:
> Adam Wolk [adam.w...@tintagel.pl] wrote: > > Hi misc@ > > > > I upgraded my mail server to an amd64 snapshot from Sep 2nd and > > found the server stuck delivering mail in the morning with > > spamassasin churning at 90% CPU usage. > > > > Quick investigation lead me to a huge bayes_toks file of 65.3G in > > /var/spampd/.spamassasin/. > > > > $ ls -alh > > total 4738352 > > drwx------ 2 _spampd _spampd 512B Sep 4 10:00 . > > drwxr-xr-x 3 _spampd _spampd 512B Sep 3 15:57 .. > > -rw------- 1 _spampd _spampd 36B Sep 4 09:53 bayes.lock > > -rw------- 1 _spampd _spampd 9.8M Sep 3 22:52 bayes_seen > > -rw------- 1 _spampd _spampd 65.3G Sep 3 22:55 bayes_toks > > > > What are your memory limits for the user/daemon class that runs > spamassassin? Touche, not set. Though it was running like that since ~December last year hence my question to misc@ if anyone noticed it behaving differently since the last release. In no way I'm assuming that something is wrong on the OS / software level - in fact I assumed that my setup was performed incorrectly by me. So far I learned a ton of useful info by asking on the list here, hope no one feels offended :) $ cat /etc/login.conf | grep -i spam $ Regards, Adam
