From owner-freebsd-questions Mon Sep 22 21:18:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA14153 for questions-outgoing; Mon, 22 Sep 1997 21:18:16 -0700 (PDT) Received: from gdi.uoregon.edu ([128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA14139 for ; Mon, 22 Sep 1997 21:18:11 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id VAA06297; Mon, 22 Sep 1997 21:17:53 -0700 (PDT) Date: Mon, 22 Sep 1997 21:17:53 -0700 (PDT) From: Doug White Reply-To: Doug White To: "Goeringer, Michael" cc: "'Steve Hovey'" , "'freebsd-questions@freebsd.org'" Subject: RE: capping forks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Sep 1997, Goeringer, Michael wrote: > In the kernel you can set CHILD_MAX=. Ofcourse this > affects the entire system so Doug may have a better solution. I couldn't think of anything offhand. I'm not familiar with the login capabilities database though, there is a ``maxproc'' item that could be used to limit the number of childs. This would be user-wide and not overridable very easily. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo