Adam Wolk [adam.w...@tintagel.pl] wrote: > On Fri, 4 Sep 2015 11:37:09 -0700 > Chris Cappuccio <ch...@nmedia.net> wrote: > > > Adam Wolk [adam.w...@tintagel.pl] wrote: > > > > > -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 > > > $ > > > > > > > Well it still runs with some class, perhaps as daemon ? > > > > I guess I'm really asking, is your login.conf modified? Post it and > > your rc.conf.local > > > > Not modified by hand. >
In that case, I wonder if you are hitting some kind of bug. I have been having regular crashes under perl in 5.8/5.8 current, I think from spamassassin (called via mailscanner). It looks like I am hitting some occasional corruption within the sqlite library after being called through the perl module.
