Detailled innfeed logging?

Russ Allbery rra at stanford.edu
Mon Mar 20 00:40:20 UTC 2006


Christoph Biedl <cbiedl at gmx.de> writes:

> I'm puzzled about it since I've started using INN ...

> Incoming articles: innd logs (into the news logfile) in detail which
> articles were received, when, from which site, which sites will receive
> it or why one was rejected.

> Outgoing articles: innfeed as the preferred transmission program is very
> silent about its activities. At least in the default configuration
> there's nothing more than an a summary in log/news.notice and
> log/innfeed.status.

> At least sometimes I'd like to have a detailled log per remote site. In
> a first step this would include the articles rejected by the peer (i.e.
> not accepted but not simply duplicate) to debug malformed group patterns
> and the like. Even more verbose but sometimes really helpful was the
> information when a given article was offerend to a peer and whether it
> was transmitted and how the response was.

> Did I oversee something in the manpages and the sources? Or is there
> nobody else who is interested in such information?

Nope, you're not missing anything.  No one has written the logging.  I'd
be happy to commit it if it were optional.

Due to the structure of innfeed, it may be a little tricky to figure out
how to get all the right information into the log.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.


More information about the inn-workers mailing list