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!corolla.OntheNet.com.au!news From: Tony Griffiths <tonyg@OntheNet.com.au> Newsgroups: comp.unix.bsd.freebsd.misc Subject: FreeBSD 2.1.x and Virtual Memory (VM) limits Date: Mon, 21 Oct 1996 11:17:37 +1000 Organization: On the Net (ISP on the Gold Coast, Australia) Lines: 17 Message-ID: <326ACF31.7FE3@OntheNet.com.au> 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) I'm having a problem with our WWW cacheing proxy (squid 1.0.???) falling over when it gets to about 128 MB virtual. The error it gets is a malloc() failure, so I presume that an attempt to expand VM has failed because of some imposed limit! I checked the sources in .../vm/ and found references to VM_MAXUSER_ADDRESS and some other defines, but could not see what "config" parameters I should change to increase the maximum virtual memory of a process. Also, I'm not sure if this is the problem because it tweaked that I have 3 swap partitions, one of 128 MB and the other 2 set at 120 MB (why 120... don't ask!). I was thinking that perhaps the maximum virtual memory of a single process is limited by the largest swap partition. Anyone knowledgeable in this area care to comment? Tony