On Fri, 2008-06-20 at 17:53 -0500, Chris wrote:
> On Friday 20 June 2008 10:14 am, Karsten Bräckelmann wrote:
> > That's the wrong way round, seriously. Do not restart SA after changes,
> > unless --lint comes out clean.
>
> Hmm, I've always understood that SA needs to be restarted to get any new
> rules
> added read, though you may be right, sa-update runs a --lint before stopping
> and starting SA.
Yes, this is true when using spamd, or any other daemonized third party
tool using the SA API directly, like amavis.
This is *not* true, when calling 'spamassassin' directly, which you do
for linting. In this case a new SA process is being started, reading all
config files from disk, entirely unrelated to a possibly running spamd.
So, while your daemonized spamd is running, you can edit the cf files
without harming the precious, busy spamd, lint your changes, and even
test them using 'spamassassin'. Only when you're happy with your
changes, restart the daemon to make it pick up the freshly changed (and
hopefully linted ;) rules.
guenther
--
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
