From owner-freebsd-security Wed Dec 6 1:17:23 2000 From owner-freebsd-security@FreeBSD.ORG Wed Dec 6 01:17:21 2000 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 7E4AC37B400 for ; Wed, 6 Dec 2000 01:17:20 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id KAA28415; Wed, 6 Dec 2000 10:17:08 +0100 (CET) (envelope-from des@ofug.org) Sender: des@ofug.org X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "James Lim" Cc: "Sebastiaan van Erk" , Subject: Re: rx list References: <20001206081549.A49341@sebster.com> <002801c05f55$0a492ac0$fa5e78cb@gchang> From: Dag-Erling Smorgrav Date: 06 Dec 2000 10:17:07 +0100 In-Reply-To: "James Lim"'s message of "Wed, 6 Dec 2000 15:20:40 +0800" Message-ID: Lines: 19 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "James Lim" writes: > You could try increasing the maxusers to 512 and later increase > your NMBCLUSTERS to prolly 50000. Maxusers is practically meaningless nowadays. It controls MAXFILES, NMBCLUSTERS, NPROC and NSFBUFS, but MAXFILES and NMBCLUSTERS are sysctl-settable (MAXFILES at runtime and NMBCLUSTERS at boot time), and there's no reason why NPROC and NSFBUFS couldn't also be set at boot time (patches are welcome!). To solve the specific problem of running out of mbufs, add kern.ipc.nmbclusters="large_number" to your /boot/loader.conf. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message