Warning, debugging, and tracing

Jeffrey M. Vinocur jeff at litech.org
Mon Mar 18 01:16:38 UTC 2002

On Sun, 17 Mar 2002, Russ Allbery wrote:

> Both the new configuration file parser and the new tradindexed
> implementation use warn() to report warning messages, so I'm planning on
> going through all of the programs in INN and setting up the warn and die
> handlers correctly, and probably converting a whole bunch of fprintfs to
> calls to warn() or die().

Ah good!

>   trace()       Possibly verbose trace information, either tracing the
>                 protocol or tracing the code.  By default there is no
>                 handler, so everything sent to trace() is ignored, but
>                 that can be changed at run-time.

...changed at run-time with some granularity, hopefully.  (e.g., per
program or module.)

For example, I'd be happy to log readers.conf processing to news.debug all
the time, but doing that results in tons of other stuff I don't care about
being logged as well.

Jeffrey M. Vinocur
jeff at litech.org

More information about the inn-workers mailing list