Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.Hawaii.Edu!ames!enews.sgi.com!news.mathworks.com!howland.erols.net!newsfeed.internetmci.com!news.webspan.net!usenet From: gpalmer@mutara.noc.webspan.net (Gary Palmer) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: odd INN behavior Date: 21 Nov 1996 01:41:41 GMT Organization: WebSpan Inc., New Jersey Lines: 18 Message-ID: <570c0l$k18@news.webspan.net> References: <5709o2$r7h@itchy.serv.net> NNTP-Posting-Host: mutara.noc.webspan.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Newsreader: knews 0.9.8 In article <5709o2$r7h@itchy.serv.net>, zeno@serv.net (Sean T. Lamont .) writes: > I've been having INN behave oddly. Firstly, which INN revision? inn 1.4 unoff 4 is the recommended one. > 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? Not personally, no, but I bet you are running into resource limits. Try puting `ulimit -d unlimited' in whatever shell script you use to start INN. Gary