From owner-freebsd-hackers Mon Dec 9 20:17:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA06423 for hackers-outgoing; Mon, 9 Dec 1996 20:17:41 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA06411 for ; Mon, 9 Dec 1996 20:17:36 -0800 (PST) Received: from misery.sdf.com ([204.244.213.33]) by misery.sdf.com with SMTP id <1774-211>; Mon, 9 Dec 1996 20:18:27 -0800 Date: Mon, 9 Dec 1996 20:18:25 -0800 (PST) From: Tom Samplonius To: "S(pork)" cc: michael butler , Jason Fesler , hackers@freebsd.org Subject: Re: Apache and huge numbers of IP's.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 9 Dec 1996, S(pork) wrote: > > This is an interesting question; a while back I posted something similar > and everyone agreed "maxusers" set to a high value would take care of max > processes and max open files... However, in setting up a medium duty > (2G/Day) dedicated webserver, I was running out of processes with maxusers > at 200. When I re-compiled the kernel with params like those below, all > was well. Could someone clarify? I'll be building another big machine > (news) soon, and I will be dealing with the same issue. > > Thanks, > > Charles Not exactly. Increasing maxusers only increases the size of system wide descriptor table. OPEN_MAX chanes the max number of open files per uid. open files per uid never changes via maxusers. CHILD_MAX sets the total number of processes per uid. You will notice that Apache runs and all its related processes run under a single uid, so you will hit the default limit of 40 processes and 64 files per uid quite quickly. The defaults are intended for a general purpose machine where you do not want users using more than their share of the processes and files. Tom > On Sun, 8 Dec 1996, michael butler wrote: > > > The number of file handles available is related to the maxusers config > > parameter. If you wish to alter that without affecting the other table > > sizes, you can add something like this to your config file .. > > > > options "CHILD_MAX=512" > > options "OPEN_MAX=512" > [snip] > > michael > > > >