Subject: INND wierdnesses
To: None <current-users@NetBSD.ORG>
From: Dave Burgess <email@example.com>
Date: 11/18/1997 18:26:27
Hi all -
In the continuing saga of the news server upgrade (I'm rolling out 1.3
slowly and it seemed to be the obvious guinea pig).
I recompiled inn-1.5.1. Unfortunately, I forgot the "#include <unistd.h>"
change. So the system ran like crap.
Thinking there might be a difference problem, I grabbed the 1.7 Version
of innd. This time, I changed the dbz.c source to include unistd.h. I
compiled it and started running it.
I was getting REALLY poor performance. As it turned out, when I
installed the new version of INND, I didn't delete the old history file
and the sucker grew to a truly gargantuos size. This also slowed the
news server to a dead crawl.
I deleted and rebuilt the history file and the system is back to normal.
The purpose of this missif is two-fold:
1) There is a newer version of INND out.
2) The database code in INND needs a patch, even in the newest
Now that the history file is synced up correctly, I am once again seen
8000 messages per hour (1000 per hour per stream at 8 streams up from 60
just a few hours ago). Also, I don't remember who asked, but I was also
getting the errors about the feed timing out. A rebuild of the history
file seems to have been the trick.
Dave Burgess Network Engineer - Nebraska On-Ramp, Inc.
*bsd FAQ Maintainer / SysAdmin for the NetBSD system in my spare bedroom
"Just because something is stupid doesn't mean there isn't someone that
doesn't want to do it...."