Jim Maul wrote:
[EMAIL PROTECTED] wrote:
Upgraded to 3.0.2 a couple of weeks ago, and just noticed that the root FS
was nearly full. I had seen this problem in the past with bayes files
growing out of control, but have been doing a "sa-learn --force-expire"
daily which helps keep that under control.
However, now I noticed that two other files that hadn't been a problem in
the past:
/root/.razor/razor-agent.log and /root/.spamassassin/auto-whitelist
I deleted the razor-agent.log and put a cron job in to delete it nightly,
but I am not sure whether I should do this with the auto-whitelist
file...does spamd consult this file every time? What's the best way to
keep it under control?
Not to quibble, but why doesn't the SA default to putting all these files
under /var or at least /usr ? Filling up the root FS can cause big
problems...
It doesnt normally fill up /root/ unless you are running spamd as root which i would REALLY not do. my .razor/ and .spamassassin/ directories are in /home/spamd/.
Hi,
Incorrect, or at least incorrect on the Linux and FBSD servers I maintain. Even running with -u username, spamd will still occasionally write files in /root/.spamassassin unless you specifically specify the path in local.cf.
In my case I run spamd with -u vpopmail, and before I added the bayes, awl and other paths in my local.cf, half of the data got written to ~vpopmail/.spamassassin and the other half to /root/.spamasassin.
Also, you may want to try running spamd with -H and specify the home directory you wish to use...perhaps /home/spamd/
-Jim
