From owner-freebsd-hackers Tue Apr 11 9:38:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id 5DD4D37BA05 for ; Tue, 11 Apr 2000 09:38:51 -0700 (PDT) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-32.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FSV00FMJ281RA@mail.uni-bielefeld.de> for freebsd-hackers@FreeBSD.ORG; Tue, 11 Apr 2000 18:38:27 +0200 (MET DST) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id MAA00303; Tue, 11 Apr 2000 12:56:43 +0200 (CEST envelope-from bjoern) Date: Tue, 11 Apr 2000 12:56:43 +0200 From: Bjoern Fischer Subject: Re: efficiency of maxproc hardlimit In-reply-to: <20000410013139.R4381@fw.wintelcom.net>; from bright@wintelcom.net on Mon, Apr 10, 2000 at 01:31:39AM -0700 To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Message-id: <20000411125643.A282@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable References: <20000410094436.A778@frolic.no-support.loc> <20000410013139.R4381@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 10, 2000 at 01:31:39AM -0700, Alfred Perlstein wrote: [...] > > main(){fork();main();} > >=20 > > leaves the machine in an unusable state (it does ping > > back, one may break into the kernel debugger, but no > > io). > >=20 > > Any way to prevent this (without harming the user)? >=20 > Please reread the documentation on limits. >=20 > cputime unlimited > filesize unlimited > datasize 256MB <- > stacksize 64MB <- > coredumpsize unlimited > memoryuse unlimited > memorylocked unlimited > maxproc 4115 > descriptors 8232 > sockbufsize unlimited >=20 > If appropriate limits are in place and you still get problems > then let us know. Already set: ... datasize 1048576 kb stacksize-cur 16384 kb ... Some more information: This happens on a diskless client (265MB RAM, lots of swap (1.2G) on the server). When I limit the stacksize to 3MB, all fork-processes fit into RAM and the situation is recoverable with some effort and `/usr/bin/killall' (Eww, that's a perl script). With a stacksize limit of 16M 64 fork processes sould easily fit into swap, so I don't think it is an out-of-swap situation. Listening to the ether on the server, I realized heavy RPC traffic (swapping, probably) and then silence. Any idea how to find out, whether swap in not really full, the client won't answer but maybe looking for some kind of NFS write errors or something? As this is a strange setup (1.2G swap via NFS) this issue in not critical at all. Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message