Hi!
As I see, my previous letter didn't come through. No problem, there were
only questions, now, I have answers and some bug.
My question was about the maintenance of a hash db, because if
unmaintained, eats up all the disk space. Now I figured out a way, that
may be correct:
Daily maintenance:
1. dspam_logrotate -a 30: delete all log entries, older than 30 days
2. delete all .sig files, older than 30 days. There is no dspam specific
tool for this, as far as I know. But 'find' can handle it easily.
Monthly maintenance:
1. dspam_clean
2. csscompress for all .css files (one per user)
3. cssclean for all .css files (one per user)
The bug is in the last two: if I have the /tmp and the dspam spool dir
on different filesystems, then both fails, and what is worse: cssclean
fails silently. Using '/tmp' as temp dierctory is hardcoded, so only
modifying the source helps.
Version 3.6.8, but I think it is the same in the cvs also.
Someone please approve that this maintenance plan is correct.
Thank you,
Peter
