Debug level?

[David Relson]

On Wed, 25 May 2005 16:03:37 -0700
David Carmean wrote:

> On Wed, May 25, 2005 at 05:51:07PM -0400, David Relson wrote:
> > On Wed, 25 May 2005 07:18:52 -0700
> > David Carmean wrote:
> > 
> > > 
> > > Is there a way to increase the debugging level without increasing the
> > > verbosity of stdout?  (looking at the source, I can't find it.)
> > > 
> > > I'm having a problem with bogofilter0.94.11 periodically hanging after 
> > > being invoked by procmail, and I want to capture debugging info.
> > 
> > Bogofilter's debug output is to stderr (unless you use "-D" which
> > changes it to stdout).
> > 
> > You might try running bogofilter via a script that would redirect
> > stderr to a file, for example:
> > 
> >   DATE="bf.`date +%s`.out"
> >   bogofilter ... 2> $FILE
> 
> 
> Yes, I can do that, but since I'm using passthrough, to get the level of 
> debugging that I want even on stderr, I end up with -vvv output on stdout 
> which ends up in my mailbox; with the intermittent nature of the 
> problem I'm having, that's going to be very disk-hungry.

Hi David,

OK, wrong solution.  Have you tried disabling stats printing (by
modifying the code)?  A patch is below.

By the way, aotto.com is no longer hosting the mailing list.  I've been
hosting it at bogofilter.org for a year and a bit.

HTH,

David

--- bogofilter.c.orig	19 May 2005 11:46:05 -0000	1.54
+++ bogofilter.c	25 May 2005 23:27:56 -0000
@@ -63,7 +63,9 @@
 
 void print_stats(FILE *fp)
 {
+/*
     msg_print_stats(fp);
+*/
 }
 
 rc_t bogofilter(int argc, char **argv)