Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.Hawaii.Edu!news.caldera.com!news.eli.net!uunet!in2.uu.net!207.22.81.9!europa.clark.net!news-peer.gsl.net!jupiter.nic.dtag.de!RRZ.Uni-Koeln.DE!news.rhrz.uni-bonn.de!news.chemietechnik.uni-dortmund.de!Uni-Dortmund.DE!Dortmund.Germany.EU.net!interface-business.de!usenet From: j@ida.interface-business.de (J Wunsch) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: Process size limits with BSDI Date: 5 Jun 1997 11:44:59 GMT Organization: interface business GmbH, Dresden Lines: 46 Message-ID: <5n68rr$6fg@innocence.interface-business.de> References: <3393AFE1.13F7@ozemail.com.au> Reply-To: joerg_wunsch@interface-business.de (Joerg Wunsch) NNTP-Posting-Host: ida.interface-business.de X-Newsreader: knews 0.9.6 X-Phone: +49-351-31809-14 X-Fax: +49-351-3361187 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:6968 Boyd Currey <boydc@ozemail.com.au> wrote: > 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?) They are wrong. First, you should look what the actual hard limits are already. That's the `limit' command in the C-Shell. Here's what i get for my FreeBSD system: j@ida 553% limit -h cputime unlimited filesize unlimited datasize 131072 kbytes stacksize 65536 kbytes coredumpsize unlimited memoryuse unlimited descriptors 1064 memorylocked unlimited maxproc 531 As you can see, the datasegment limit maxes out at 128 MB for me. If your hard limits differ from the soft limits (without the -h), you might consider raising them before starting your server processes (supposedly with the ulimit builtin of /bin/sh), or you might have a look at the login class that applies to your server process (/etc/login.conf, plus the login class field in the password file for the respective user). Only if your hard limits are too small, you gotta tune your kernel. The kernel options you mention above look reasonable, though i'm not fully sure about the exact naming in BSD/OS. Regarding the brain limitations of the people in your design department, have them log into ftp.cdrom.com some day, and look at their hardware equipment. :-) (ftp://ftp.cdrom.com/archive-info/wcarchive.txt) -- J"org Wunsch Unix support engineer joerg_wunsch@interface-business.de http://www.interface-business.de/~j