From owner-freebsd-stable Wed Nov 6 00:52:07 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA02560 for stable-outgoing; Wed, 6 Nov 1996 00:52:07 -0800 (PST) Received: from birdland.rhein-neckar.de (root@birdland.rhein-neckar.de [193.197.88.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA02342 for ; Wed, 6 Nov 1996 00:50:07 -0800 (PST) Received: from localhost (bsd@localhost) by birdland.rhein-neckar.de (8.7.5/8.7.3) with SMTP id JAA09556; Wed, 6 Nov 1996 09:45:38 +0100 (MET) Date: Wed, 6 Nov 1996 09:45:37 +0100 (MET) From: BSD Mailinglisten-User To: Heiko Blume cc: stable@FreeBSD.org Subject: Re: innd can't malloc - why? In-Reply-To: <199611051250.NAA11668@NS.Contrib.Com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 5 Nov 1996, Heiko Blume wrote: > hello > > maybe i'm a little ignorant, but my innd lately vanishes very often > our of the blue (i.e. not during expire) telling me > > Nov 5 07:52:15 news innd: ME cant remalloc 8392960 bytes Cannot allocate memory [...] > for the life of me i can't see why it should fall short of memory. > here's some data: [...] > 23038 news -6 4 65M 47M sleep 11:15 6.90% 6.90% innd ^^^ this is your problem There are several hard coded kernel parameters about the maximum sizes of processes. I had the same problem, but after a little searching in the mailinglist archives in www.freebsd.org (you didn't do that, didn't you???) I found out that changing the following parameters in /usr/src/sys/i386/include/vmparam.h did the trick for me: DFLDSIZE to 128M and MAXSSIZE to 128M Both are 64M in the default config. YMMV, Martin | Martin Jangowski E-Mail: maja@birdland.rhein-neckar.de | | Voice: +49 621/53 95 06 Fax: +49 621/53 95 07 | | Snail Mail: Koenigsbacher Str. 16 D-67067 Ludwigshafen Germany | | RNInet e.V. Rhein-Neckar Internet |