From ylo@trance.olari.clinet.fi  Thu Jan 25 15:13:51 1996
Received: from who.cdrom.com (who.cdrom.com [192.216.222.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA16120
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 25 Jan 1996 15:13:51 -0800 (PST)
Received: from trance.olari.clinet.fi (trance.olari.clinet.fi [194.100.1.134])
          by who.cdrom.com (8.6.12/8.6.11) with ESMTP id PAA09543
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 25 Jan 1996 15:12:24 -0800
Received: (from ylo@localhost) by trance.olari.clinet.fi (8.6.12/8.6.12) id BAA24436; Fri, 26 Jan 1996 01:17:08 +0200
Message-Id: <199601252317.BAA24436@trance.olari.clinet.fi>
Date: Fri, 26 Jan 1996 01:17:08 +0200
From: Tatu Ylonen <ylo@trance.olari.clinet.fi>
Reply-To: ylo@trance.olari.clinet.fi
To: FreeBSD-gnats-submit@freebsd.org
Subject: Default limits for number of processes per user ridiculously low
X-Send-Pr-Version: 3.2

>Number:         971
>Category:       kern
>Synopsis:       Default limits for number of processes per user ridiculously low
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 25 15:20:02 PST 1996
>Closed-Date:    Sat Jan 11 11:01:05 PST 1997
>Last-Modified:  Sat Jan 11 11:03:04 PST 1997
>Originator:     Tatu Ylonen
>Release:        FreeBSD 2.1-STABLE i386
>Organization:
Helsinki University of Technology
>Environment:

	Single-user machine, i486-100, 24M ram, 4GB disk.
	Kernel with maxusers 100.

>Description:

	The default maxusers value in the distribution kernel is too low for
	use as a single-user workstation.

	Even when maxusers is increased, the limit for number of processes
	per user does not appear to increase, but must be increased with
	"limit maxproc 1000" or something like that.  The default limit
	appears to be 40, which isn't good for anything.  Count X, a
	few xterms, netscape or two, a few emacses, some rsh/ssh processes,
	and a compilation or debugger.  It is not possible to use a machine
	with maxproc 40, and changing it is annoying since if you don't
	do it at login, new xterms and emacses started from window manager
	will again have the minuscule limit.

>How-To-Repeat:
>Fix:
	
	Make the default soft limit grow with maxusers.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: scrappy 
State-Changed-When: Mon Oct 21 23:33:50 PDT 1996 
State-Changed-Why:  

Dust off the cobwebs - Confirm Status 
State-Changed-From-To: feedback->open  
State-Changed-By: scrappy 
State-Changed-When: Tue Oct 22 14:17:57 PDT 1996 
State-Changed-Why:  

Still existent.  The problem is that simply bumping the number is 
inappropriate.  The 40 might already be too high as a default for an 
386/sx16 with 4 MB RAM (bottom end of what we are supporting), while 
it is plain stupid for an i686/200 with 128 MB RAM.  So, the actual 
default should be calculated based on the size of the machine, with an 
option to allow the admin overriding it from the config file. 

I once thought loud about this, but never got round to really 
implement it.  Might look like a nice pet project for somebody over 
the weekend. 

-- 
cheers, J"org 

State-Changed-From-To: open->closed 
State-Changed-By: mpp 
State-Changed-When: Sat Jan 11 11:01:05 PST 1997 
State-Changed-Why:  
The new login.conf changes allow this to be easily 
changed. 
>Unformatted:
