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 Message-ID: <Pine.NEB.3.96.970823231021.567B-100000@thelab.hub.org> In-Reply-To: <Pine.BSF.3.95.970817210142.27023X-100000@alive.znep.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96.970823231021.567B-100000>