From owner-freebsd-hackers  Sat Aug 23 19:11:12 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA29118
          for hackers-outgoing; Sat, 23 Aug 1997 19:11:12 -0700 (PDT)
Received: from thelab.hub.org (root@ppp-142.halifax-01.ican.net [206.231.248.142])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA29099
          for <hackers@FreeBSD.ORG>; Sat, 23 Aug 1997 19:11:05 -0700 (PDT)
Received: from thelab.hub.org (scrappy@localhost [127.0.0.1]) by thelab.hub.org (8.8.7/8.8.2) with SMTP id XAA00587; Sat, 23 Aug 1997 23:10:52 -0300 (ADT)
Date: Sat, 23 Aug 1997 23:10:52 -0300 (ADT)
From: The Hermit Hacker <scrappy@hub.org>
To: Marc Slemko <marcs@znep.com>
cc: hackers@FreeBSD.ORG
Subject: Re: [HACKERS] innd remalloc failure *after* setting MEMDSIZ
In-Reply-To: <Pine.BSF.3.95.970817210142.27023X-100000@alive.znep.com>
Message-ID: <Pine.NEB.3.96.970823231021.567B-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 17 Aug 1997, Marc Slemko wrote:

> On Sun, 17 Aug 1997, The Hermit Hacker wrote:
> 
> > 
> > Hi...
> > 
> > 	After going through "the archives", and finding the suggestion of increasing
> > MEMDSIZ to 256Meg, and recompiling/running the new kernel...I'm still getting
> > the remalloc 'crash' with innd.
> > 
> > 	The kernel is 2.2.2-RELEASE, innd is 1.6b3...I have an 'unlimit' at the
> > beginning of ~news/etc/rc.news...
> 
> What does a ulimit -a run from rc.news after your unlimit say?
> 
> It should be MAXDSIZ; was the just a typo, or did you set the wrong thing?

	typo :(  Just checked, and it was MAXDSIZ that I sent...

> What does the inn log report?

	Just the remalloc() error, which varies for each time it happens...


Marc G. Fournier                                
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org