On 4/25/2012 2:38 AM, Chad Leigh Shire.Net LLC wrote:
I have SA 3.3.2 installed on FreeBSD 9. This was installed from "source" and
not the package or port. I have some different requirements and so built it myself.
I run a bunch of FreeBSD jails on a given system, and have a new area I call
/usr/public which gets mounted inside each jail. The software gets built and
installed here, but I work to set things up so that it reads config files and
uses local space in /usr/local for each system.
I am having an issue with SA 3.3.2 on a new install (my old servers were
running an old SA 3.x that was pre sa-update) where it claims the rules are not
found. This includes spamassassin and spamd
If I run spamassassin manually here is the debug output (first part):
spamassassin --configpath=/usr/local/etc/mail/spamassassin/ -D<
1335330803.H270347P64367.mail.shire.net
Apr 25 00:26:06.303 [64987] dbg: logger: adding facilities: all
Apr 25 00:26:06.303 [64987] dbg: logger: logging level is DBG
Apr 25 00:26:06.303 [64987] dbg: generic: SpamAssassin version 3.3.2
Apr 25 00:26:06.304 [64987] dbg: generic: Perl 5.012004, PREFIX=/usr/public,
DEF_RULES_DIR=/usr/public/share/spamassassin,
LOCAL_RULES_DIR=/usr/local/etc/mail/spamassassin,
LOCAL_STATE_DIR=/usr/local/var/spamassassin
The LOCAL_STATE_DIR is my belief.
If you run sa-update --help, the help text will be compiled for your
default rules
For example, on a more stock trunk compilation:
--updatedir path Directory to place updates, defaults to the
SpamAssassin site rules directory
(default: /var/lib/spamassassin/3.004000)
Testing 3.3.2 with perl 5.14:
--updatedir path Directory to place updates, defaults to the
SpamAssassin site rules directory
(default:
/usr/local/perl5.14.0/var/spamassassin/3.003002)
That should tell you where they will end up.
Regards,
KAM
