*BSD News Article 83500


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: odd INN behavior
Date: Sun, 24 Nov 1996 16:17:38 +1000
Organization: On the Net (ISP on the Gold Coast, Australia)
Lines: 21
Message-ID: <3297E882.6CE8@OntheNet.com.au>
References: <5709o2$r7h@itchy.serv.net>
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: "Sean T. Lamont ." <zeno@serv.net>

Sean T. Lamont . wrote:
> 
> I've been having INN behave oddly.
> 
> Every so often, it will fail on a realloc() call, citing "cannot realloc
> x bytes). x is usually in the range of 5-20 megabytes. This has been increasing
> as of late, but the distressing thing is the allocation failure ; at the times
> that it happens, there is usually 200-300 megabytes of swap available
> on the system, and it's failing on 15M allocations?
> 
> Has aybody seen this?
>
Yes, but not with INN!  In my case it was Squid (WWW cacheing proxy)
that couldn't expand it's data segment VM.  The fix was to rebuild the
kernel with the following options-

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


Tony