> > I'd feel more comfortable if some FreeBSD master guru would > > take a look and have a final say. > > Any master guru's out there?
I consulted one, a FreeBSD maintainer from the office next door :) After reading our thread, his answer was a clear and decisive: /var/db/spamassasin (but for confirmation a [EMAIL PROTECTED] ML could be consulted) > Things to consider: multiple spool, some like /var for logs and /var/db > Who backs up /var/db/ and if LOCALSTATE dir contents overwritten during > sa-update, who cares about backing it up? > Backups: where do automated, normal backups use as source > (I don't back up /var/db due to the transitory nature of the files) > I don't back up /usr/local/libdata either.. Maybe I should. Rules are updated periodically, possibly automated, so they can't go under /usr (or /usr/local or /etc) which could in principle be mounted read-only. The /var is indended for frequently changing data. /usr/local/share/spamassassin is a perfect spot for what it already holds. The /usr/local/libdata/spamassassin would be appropriate just as well for these distribution rules, but not appropriate for frequently changing data. /usr/local/lib/spamassassin is not a good place. Comparing rules (in a textual config files syntax) to libraries is far-fetched. And remember, /usr could be read-only. Files under /usr/local/lib are definitely not intended to be frequently updated. As for /var/db/spamassassin, comparing it to /var/db/clamav is a perfect analogy, these rules represent a knowledge database to SA, just as virus database is to ClamAV. And it is automatically generated, needs no backup. Mark
