From owner-freebsd-security Thu Apr 19 10:58: 1 2001 Delivered-To: freebsd-security@freebsd.org Received: from urdvg001.cms.usa.net (urdvg001.cms.usa.net [165.212.11.1]) by hub.freebsd.org (Postfix) with SMTP id BD1AE37B423 for ; Thu, 19 Apr 2001 10:57:56 -0700 (PDT) (envelope-from briant@packeteer.com) Received: (qmail 23621 invoked from network); 19 Apr 2001 17:57:55 -0000 Received: from uadvg129.cms.usa.net (165.212.11.129) by corprelay.cms.usa.net with SMTP; 19 Apr 2001 17:57:55 -0000 Received: (qmail 19260 invoked by uid 0); 19 Apr 2001 17:57:55 -0000 Received: USA.NET MXFirewall, messaging filters applied; Thu, 19 Apr 2001 17:57:54 GMT Received: from packeteer.com [207.78.98.2] by uadvg129 (ASMTP/briant@postoffice.packeteer.com) via mtad (53CM.0401.1.03) with ESMTP id 365FDsR6z0319M20; Thu, 19 Apr 2001 17:57:51 GMT Message-ID: <3ADF2757.DF2C0A88@packeteer.com> Date: Thu, 19 Apr 2001 10:58:47 -0700 From: Brian Tiemann Organization: Packeteer, Inc. X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: security@freebsd.org Subject: Re: maxusers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 19 Apr 2001, Dag-Erling Smorgrav wrote: > There is no relation between maxusers and the number of ptys > available. In fact, there is practically no relation between maxusers > and anything of interest in the kernel. I believe the only value > affected by maxusers that can't be tuned at boot- or run-time is the > maximum size of the process table. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message