Date: Wed, 6 Nov 1996 09:45:37 +0100 (MET) From: BSD Mailinglisten-User <bsd@birdland.rhein-neckar.de> To: Heiko Blume <src@NS.Contrib.Com> Cc: stable@FreeBSD.org Subject: Re: innd can't malloc - why? Message-ID: <Pine.BSF.3.94.961106093613.9480A-100000@birdland.rhein-neckar.de> In-Reply-To: <199611051250.NAA11668@NS.Contrib.Com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.94.961106093613.9480A-100000>