From owner-freebsd-stable Sun Sep 19 19:35:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 4516F15279 for ; Sun, 19 Sep 1999 19:35:38 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Sun, 19 Sep 1999 19:35:37 -0700 From: "David Schwartz" To: "Kip Macy" , Subject: RE: kern.maxfiles and kern.maxfilesperproc Date: Sun, 19 Sep 1999 19:35:37 -0700 Message-ID: <002501bf0310$d2700520$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-reply-to: Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is kern.maxfiles the total number of files that can be open on the system > at one time? If so it seems very silly that by default it is the same > number as kern.maxfilesperproc -- meaning that any process can use up the > total number of files available to the system. > Thanks. > > -Kip These are the default values for maximums. They're not intended to protect your system against resource starvation by a malicious process (since they apply to root as well as normal users). And actually, it makes a lot of sense. It's not unusual for a server to really only have one process or set of processes that you care about. For example, for a web server, all you really care about is Apache. For an SMB file server, Samba. So it's reasonable that the two limits be similar. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message