You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@spamassassin.apache.org by Matthias Leisi <ma...@leisi.net> on 2006/12/20 20:42:01 UTC

sa-update & spamd: updatedir

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I can specify "sa-update --updatedir path" to use something other than
the default (eg /var/lib/spamassassin/<version>). However, I can not do
the same for spamd(8) and spamassassin(1) -- they have LOCAL_STATE_DIR
substituted at make time.

I know that I can trick spamd & spamassassin into using whatever
directory I like for whatever rule files, but wouldn't it make sense to
make this configurable through the command line (or some system-wide
setting) in spamd + spamassassin as well?

Note: Applies to both 3.1.7 and SVN, if I looked correctly.

- -- Matthias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFFiZIJxbHw2nyi/okRAujAAKDMsW3m85UWqu05Ij0KkcLEblYoVQCfQknT
8GJQ8Ob6Lg5oIIggpD4MKrU=
=v8xM
-----END PGP SIGNATURE-----

Re: sa-update & spamd: updatedir

Posted by Theo Van Dinter <fe...@apache.org>.

On Wed, Dec 20, 2006 at 08:42:01PM +0100, Matthias Leisi wrote:
> I know that I can trick spamd & spamassassin into using whatever
> directory I like for whatever rule files, but wouldn't it make sense to
> make this configurable through the command line (or some system-wide
> setting) in spamd + spamassassin as well?

A better question is: why are you using updatepath?

fwiw, you can use spamd's -C to point at the new dir, which will break
TextCat, but ...

-- 
Randomly Selected Tagline:
 "Face it, Fry, baseball was as boring as mom and apple pie. That's why they
 jazzed it up." -Leela 
  "Boring? Baseball wasn't...hmmm, so they finally jazzed it up." -Fry