From owner-freebsd-stable Tue Sep 21 16:42:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from forty-two.egroups.net (adsl-63-193-215-235.dsl.snfc21.pacbell.net [63.193.215.235]) by hub.freebsd.org (Postfix) with ESMTP id 2084F1550A for ; Tue, 21 Sep 1999 16:42:40 -0700 (PDT) (envelope-from gsutter@forty-two.egroups.net) Received: (from gsutter@localhost) by forty-two.egroups.net (8.9.3/8.9.2) id QAA28109; Tue, 21 Sep 1999 16:42:39 -0700 (PDT) (envelope-from gsutter) Date: Tue, 21 Sep 1999 16:42:39 -0700 From: Gregory Sutter To: Kip Macy Cc: stable@freebsd.org Subject: Re: kern.maxfiles and kern.maxfilesperproc Message-ID: <19990921164238.E49731@forty-two.egroups.net> References: <19990921161540.D49731@forty-two.egroups.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Kip Macy on Tue, Sep 21, 1999 at 04:23:19PM -0700 Organization: Zer0 Approved: graham.spanier Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 21, 1999 at 04:23:19PM -0700, Kip Macy wrote: > Thanks. Although having maxfiles == maxfilesperproc might make sense for > special cases e.g. a machine completely dedicated to one process -- It is > dangerous at best for the general case. Any malicious program can make a > machine running FreeBSD non-functional. The default should be set with the > average user in mind, namely protecting him from himself. Agreed, although this protects not just the average user but also everyone who doesn't want to fool with login.conf or reset their sysctls or change their source, just to change a poorly-thought- out default. Greg -- Gregory S. Sutter "How do I read this file?" mailto:gsutter@pobox.com "You uudecode it." http://www.pobox.com/~gsutter/ "I I I decode it?" PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message