*BSD News Article 84770


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.syd.connect.com.au!news.bri.connect.com.au!fjholden.OntheNet.com.au!news
From: Tony Griffiths <tonyg@OntheNet.com.au>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: memory limits for single process ?
Date: Sun, 15 Dec 1996 17:27:44 +1000
Organization: On the Net (ISP on the Gold Coast, Australia)
Lines: 37
Message-ID: <32B3A870.5EBC@OntheNet.com.au>
References: <01bbe86d$7681adb0$2c411bcc@shame>
Reply-To: tonyg@OntheNet.com.au
NNTP-Posting-Host: swanee.nt.com.au
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0 (WinNT; I)
To: Raul Zighelboim <mango@communique.net>
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:32634

Raul Zighelboim wrote:
 
> My news server (1nn 1.5) dies last night with:
> SERVER cant remalloc 393216 bytes Cannot allocate memory

Increasing the default and maximum data segment sizes can be done with
kernel 'options' in your config file.  Eg.

options         "MAXDSIZ=536870912"     #Maximum Data Segment size 512MB
options         "DFLDSIZ=268435456"     #Default Data Segment size 256MB

> 
> And:
> 
> According to the FAQ:
> -------
> Subject: (5.24) ME cant remalloc xx bytes Cannot allocate memory
> 
> This probably means that innd wants to grow bigger than what the
> actual limit for a single process is.
> To solve this either rebuild your kernel with a different default max,
> or add "unlimit datasize" to the beginning on your rc.news file.

ulimit is the 'sh' command to adjust certain process limits.  There
might be 'sysctl' variables as well.

> On some OS (e.g. FreeBSD 2.1.x) there might be some problems when
> using the supplied malloc. Linking with -lgnumalloc helped (after Joe
> Greco <jgreco@ns.sol.net>).
> -------

I don't know why you need to do this for inn.  We run inn here and I
havn't had to increase the data segment sizes for at all and I've never
seen it fall over with a malloc() error!  Now Squid is another matter
altogether...  it's a REAL memory hog!!!

Tony