On Sat, May 13, 2006 at 10:57:11AM -0700, Bart Schaefer wrote: > Apparently the conflict is only that RDJ restarts spamd automatically, > but sa-update does not.
I don't believe there's a conflict there, but yes, sa-update does not auto-restart spamd. > Default configuration data is loaded from the first existing directory > in: > > /var/lib/spamassassin/3.001001 > /usr/share/spamassassin > /usr/share/spamassassin > /usr/local/share/spamassassin > /usr/share/spamassassin > > (Why is /usr/share/spamassassin in that list three times?) Technically the list is: '__local_state_dir__/spamassassin/__version__', '__def_rules_dir__', '__prefix__/share/spamassassin', '/usr/local/share/spamassassin', '/usr/share/spamassassin', Where __def_rules_dir__ == /usr/share/spamassassin, and __prefix__ == /usr. So based on your install the /usr/share/spamassassin directory is in there 3 times, but each of those could be different depending on the installation. > Well, guess what. "sa-update" creates the > /var/lib/spamassassin/3.001001 directory if it does not exist, rather > than finding the directory that does exist and using that. I didn't Of course. sa-update *only* uses the /var/lib area. It doesn't care about what other rules you already have installed or where they are. > Yet the CPAN install of spamassassin uses /usr/share/spamassassin for > the installation. Surely the install ought to use the same directory > that sa-update is going to create, or vice-versa? No. sa-update is optional and writes stuff to its own area separate from the installation of SA. You may want to check out http://wiki.apache.org/spamassassin/RuleUpdates which talks about sa-update, how it works, etc. -- Randomly Generated Tagline: Support Medical Examiners. Die strangely.
pgpwAuepZuAwe.pgp
Description: PGP signature
