I don't believe there is a "best practice" location for any of spamdyke's files. I see where the documentation mentions /var/tmp, but that's just an example. On my own server, I keep everything under /usr/local/spamdyke, but many others use /var/qmail/spamdyke or /home/vpopmail/spamdyke... it's very dependent on how your server is setup. But considering that a huge graylist folder structure on a busy server can consume all of a filesystem's inodes (making it impossible to create new files even though "df" reports lots of free space), I'd suggest putting your graylist folders somewhere other than your root drive. And definitely use a script to clean out old graylist files/folders on a regular basis -- there is an example command here: http://www.spamdyke.org/documentation/FAQ.html#SUGGESTION5
-- Sam Clippinger On Jun 7, 2015, at 8:26 AM, Les Fenison via spamdyke-users <spamdyke-users@spamdyke.org> wrote: > I have noticed a very high cpu load lately when tmpwatch runs and it takes > forever to finish. Then I found out why. the /var/tmp/graylist.d > directory was HUGE. After removing it, tmpwatch now takes less than a > minute to run. It use to be 6 hours!!!! > > So, what is the best practice? The spamdyke docs said to put it in /var/tmp > but from what I just experienced, that doesn't sound like such a good idea. > Is there any reason I can't just put it in /var/graylist.d ? Any > recommendations? > _______________________________________________ > spamdyke-users mailing list > spamdyke-users@spamdyke.org > http://www.spamdyke.org/mailman/listinfo/spamdyke-users
_______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
