Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!newsfeed.internetmci.com!news.webspan.net!usenet From: Gary Palmer <gpalmer@SPAM.webspan.net> Newsgroups: news.software.nntp,comp.unix.bsd.freebsd.misc Subject: Re: libgnumalloc Date: 11 Jun 1997 18:35:04 GMT Organization: WebSpan Inc., New Jersey Lines: 13 Message-ID: <5nmr4o$800@news.webspan.net> References: <339C538C.167E@ispnews.com> <5nk9oe$661$1@flea.best.net> <339E94BB.41C6@ispnews.com> NNTP-Posting-Host: orion.webspan.net X-Report-Abuse-To: abuse@mail.webspan.net NNTP-Posting-Date: 11 Jun 1997 14:35:04 EDT Xref: euryale.cc.adfa.oz.au news.software.nntp:33624 comp.unix.bsd.freebsd.misc:42768 In article <339E94BB.41C6@ispnews.com>, Phil Crown <pcrown@ispnews.com> wrote: >[posted and mailed] >I am getting "cant remalloc xxxxxxxxx bytes" errors when trying to run >INN's expireover, and the a FAQ suggests trying gnumalloc. You do not want GNU malloc. phkmalloc, which is standard in libc in FreeBSD 2.2 is generally faster (IIRC). What is probably happening is you are running into either a oversized .overview file, and don't have enough RAM to load it, or you have the resource limits on the user running the expireover too low. If you are running it by hand, try doing an `unlimit' command first Gary