From owner-freebsd-security Fri Apr 20 0:47:25 2001 Delivered-To: freebsd-security@freebsd.org Received: from silby.com (adam042-060.resnet.wisc.edu [146.151.42.60]) by hub.freebsd.org (Postfix) with ESMTP id F085B37B424 for ; Fri, 20 Apr 2001 00:47:22 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 25499 invoked by uid 1000); 20 Apr 2001 07:47:21 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Apr 2001 07:47:21 -0000 Date: Fri, 20 Apr 2001 02:47:21 -0500 (CDT) From: Mike Silbersack To: Brian Tiemann Cc: Subject: Re: maxusers In-Reply-To: <3ADF2757.DF2C0A88@packeteer.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 19 Apr 2001, Brian Tiemann wrote: > Would it be a horrible idea to change the name of the key in the > config file? Maybe to something less likely to cause this (very common > and > understandable) error-- like, say, RSRCLIM (resource limit)? > > Brian Changing MAXUSERS to something else would probably just aggravate a lot of people and not help much. A better solution (which has already been done for the mbuf system) is to turn the setting MAXUSERS into tuneables that can be set in loader.conf. And once that's complete, it leaves the door open for someone to add auto-tuning based on ram size. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message