Bugs with CURRENT.

Jeffrey M. Vinocur jeff at litech.org
Thu Feb 28 00:19:25 UTC 2002



On Wed, 27 Feb 2002, William F. Maton wrote:

> 	I'm using INN-CURRENT-20020224, as part of my IPv6 work.  So far,
> I'm noticing one bug:  innreport takes forever to run.

Hrm.  Mine runs just fine (takes about eight minutes, but I'm a small
site).  The only change we made to innreport in the IPv6 patch is:

-    if ($left =~ /(\S+) connect$/o) {
+    if ($left =~ /(\S+) (\([0-9a-fA-F:.]*\) )?connect$/o) {

and I don't see how that would get you any running time issue.  Does
somebody who really knows Perl want to comment if that should be a
problem?


> syslogd is going nuts after some 10 minutes of initial INN startup.  I
> find the following entries in /var/log/syslog:
>
> Feb 27 18:56:34 crc-news innd: SERVER internal SITEreader
> Feb 27 18:56:43 crc-news last message repeated 168588 times

Hrrrrrm.  (I don't see this either, of course.)  I haven't peered much at
the innd internals, but that appears to be a this-should-never-happen
message from innd/site.c:SITEreader() -- if no one else has an idea I'll
try to take a better look later.)


-- 
Jeffrey M. Vinocur
jeff at litech.org




More information about the inn-bugs mailing list