From owner-freebsd-hackers  Tue Aug 26 10:14:03 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA22761
          for hackers-outgoing; Tue, 26 Aug 1997 10:14:03 -0700 (PDT)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA22755
          for <freebsd-hackers@freebsd.org>; Tue, 26 Aug 1997 10:13:56 -0700 (PDT)
Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1)
	id 0x3P9c-00079e-00; Tue, 26 Aug 1997 10:11:44 -0700
Date: Tue, 26 Aug 1997 10:11:43 -0700 (PDT)
From: Tom Samplonius <tom@sdf.com>
To: Kachun Lee <kachun@zippo.com>
cc: scrappy@hub.org, freebsd-hackers@freebsd.org
Subject: Re: [HACKERS] innd remalloc failure *after* setting MEMDSIZ
In-Reply-To: <199708261615.JAA10060@dopey.pathlink.com>
Message-ID: <Pine.BSF.3.95q.970826100955.27380B-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Tue, 26 Aug 1997, Kachun Lee wrote:

> remalloc error is usually cause by the channel feed processes (the Tc in the 
> newsfeeds file) not keeping up. The common ones are overchan, overview, 
> nntplink and innfeed. Let your innd run for several hours and do a 'ctlinnd 
> flush <feed-name>' on each of your Tc feeds, and see if any one writes a 
> backlog file in your out.going directory.

  Or you could just do a 'ctlinnd feedinfo "" ' to see how much is
backlogged for every channel.

  You would do well to put an upper bound (flag "S") on every channel,
just to make sure that innd will not try to buffer too much.

Tom