Re: svn commit: r1150225 - /spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/Check.pm

[Karsten Bräckelmann <gu...@rudersport.de>]

On Mon, 2011-07-25 at 10:04 +0300, Henrik Krohns wrote:
> > On Jul 24, 2011, at 2:55 PM, John Hardin wrote:

> > > My change gives very basic elapsed time stats only if a specific debugging 
> > > channel is enabled. I view it as equivalent to the "rules" debug channel 
> > > logging the text that the rule matched. This sort of thing will be 
> > > regularly used by many end users when interactively troubleshooting 
> > > performance problems, and does not require any changes to the production 
> > > system's configuration (such as enabling a new plugin).

> Checking rule timings should not be a task that requires lot of effort. I
> don't want to go enabling and disabling plugins each time for a simple task. 

Answering both -- you don't have to muck with your site-wide .pre files,
to fire up a one-time 'spamassassin' debugging run. Even loadplugin
lines do work in a simple --cf option.

(Just like loadplugin isn't actually required to be in .pre files. It
works just fine in .cf files, as long as all rules and options that
depend on the plugin are parsed after that.)


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
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; }}}