From owner-freebsd-questions@FreeBSD.ORG  Sat Apr  5 10:23:00 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 021C837B401
	for <freebsd-questions@freebsd.org>;
	Sat,  5 Apr 2003 10:23:00 -0800 (PST)
Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl
	[62.251.72.224])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 328D543F85
	for <freebsd-questions@freebsd.org>;
	Sat,  5 Apr 2003 10:22:50 -0800 (PST)
	(envelope-from dirkx@webweaving.org)
Received: from foem (foem [10.11.0.2])h35IMmLG041753;
	Sat, 5 Apr 2003 20:22:48 +0200 (CEST)
	(envelope-from dirkx@webweaving.org)
Date: Sat, 5 Apr 2003 20:22:48 +0200 (CEST)
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
X-X-Sender: dirkx@foem.leiden.webweaving.org
To: Adam <blueeskimo@gmx.net>
In-Reply-To: <1049566249.91991.18.camel@jake>
Message-ID: <20030405202158.B34257-100000@foem.leiden.webweaving.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-questions@freebsd.org
Subject: Re: Protecting against fork bombs
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2003 18:23:00 -0000



On 5 Apr 2003, Adam wrote:

> In light of the recent problems with cyclic Xft dependencies, it has
> become painfully obvious how quickly a fork bomb can bring my computer
> to a complete halt.

	ulimit -u 100

does not do that for you adequately enough (or setting the same in
/etc/login.conf (field maxproc)) ??

Dw/