Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!newsfeed.internetmci.com!newsxfer2.itd.umich.edu!agate!violet.berkeley.edu!jkh From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: How to check memory usage Date: 5 Jan 1996 01:17:45 GMT Organization: University of California, Berkeley Lines: 21 Message-ID: <4chu7p$ca2@agate.berkeley.edu> References: <4chirk$1ca@lainet2.lainet.com> NNTP-Posting-Host: violet.berkeley.edu In article <4chirk$1ca@lainet2.lainet.com>, Sassan Behzadi <sassan@lainet.com> wrote: >30 daemons had been the limit (anything more than that would fail >to start with "fork failed - no resources") so we upgraded the 32MB >system to 64MB. The system sees the additional memory and so does >the OS (at least during the bootup), but even with the addition of >32MB we can only go up to 35 daemons. It just doesn't add up. Each Actually, you've been hitting a "soft limit" all along. You can change this with the `limit' builtin in csh (`ulimit' in bash) for a specific instance of the shell or, as is more likely to be useful in your case, the whole system by changing a couple of parameters in your kernel configuration file and rebuilding the kernel. See /sys/i386/conf/LINT for a list of some of the values you can tweak, in particular this one: options "CHILD_MAX=128" (128 is a good value for a server, BTW). Jordan