From owner-freebsd-questions Tue Oct 29 08:49:57 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA07759 for questions-outgoing; Tue, 29 Oct 1996 08:49:57 -0800 (PST) Received: from revelstone.jvm.com (revelstone.jvm.com [207.98.213.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA07751 for ; Tue, 29 Oct 1996 08:49:53 -0800 (PST) Received: (from fbsdlist@localhost) by revelstone.jvm.com (8.7.5/8.6.12) id LAA07059; Tue, 29 Oct 1996 11:49:52 -0500 (EST) Date: Tue, 29 Oct 1996 11:49:52 -0500 (EST) From: Cliff Addy To: questions@freebsd.org Subject: maxuser > 64 warning Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We're building a custom kernel for a busy webserver. We set the maxusers to 256, the CHILD_MAX to 256, and the OPEN_MAX to 256. When we run config, we get a warning that maxusers is over 64. Is there a problem with maxusers over 64? We want to insure that the kernel tables are large enough to handle a large number of processes (we've already had problems with full tables) and that we can avoid insufficient file handle problems. The server is has 64 megs of RAM, most of which is used as cache, so a large kernel wouldn't seem to be a problem. Would the kernel be significantly slower? Cliff