Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!newsfeeds.sol.net!news.webspan.net!news1.exit109.com!not-for-mail From: Jeremy <jeremy@exit109.com> Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: Process size limits with BSDI Date: 6 Jun 1997 00:20:15 GMT Organization: Still working on it... Lines: 31 Message-ID: <5n7l3v$5dj$8@news1.exit109.com> References: <3393AFE1.13F7@ozemail.com.au> NNTP-Posting-Host: ns.exit109.com X-Newsreader: trn 4.0-test58 (13 May 97) Originator: jeremy@exit109.com (Jeremy) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:6970 Boyd Currey <boydc@ozemail.com.au> wrote: > Our primary DNS is a dedicated server with a pentium processor >and 128M RAM, and at the moment, it seems to reach a process size >(reported by 'ps' or 'top' etc) of approximately 64M, and then >dies with a cannot malloc error. People have been reporting similar >problems with squid running on BSDI platforms. > > I have read that with careful tuning of kernel parameters such >as DFLDSIZ, DFLSIZ, MAXDSIZ, etc, that this limit can be increased. >I forwarded this advice onto our design department and they reported >that it would not help, and the 64M limit was imposed by the OS and its >hardware (namely the 386 code base?) > > My questions are, is this all true? No. The 64M hard limit is in the kernel. If you need more than 64 megs, add something like this to the kernel config file: options "MAXDSIZ=\(96*1024*1024\)" and rebuild the kernel. The above line gives you 96 megs to play with, which is what I'm using on my news machine. (Just make sure you're removing any soft limits with "unlimit" or a similar command, depending on the shell.) -- Jeremy | jeremy@exit109.com "Okay, now you're just abusing sarcasm." --Buffy