From owner-freebsd-hackers  Mon Feb 27 12:26:48 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA04944 for hackers-outgoing; Mon, 27 Feb 1995 12:26:48 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA04938 for <freebsd-hackers@freefall.cdrom.com>; Mon, 27 Feb 1995 12:26:42 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id HAA17707; Tue, 28 Feb 1995 07:23:47 +1100
Date: Tue, 28 Feb 1995 07:23:47 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199502272023.HAA17707@godzilla.zeta.org.au>
To: ghelmer@alpha.dsu.edu, guido@gvr.win.tue.nl
Subject: Re: Max procs per user
Cc: freebsd-hackers@freefall.cdrom.com
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>particular kernel).  When looking through kernel include files, it
>appeared that there is a limit of 40 procs per user ("#define MAXUPRC
>CHILD_MAX" in /sys/sys/param.h, where CHILD_MAX is 40 in syslimits.h), but
>I was hoping there was a way around that.  Perhaps I have to change the
>include files and rebuild the kernel? 

User setrlimit(2), or `ulimit' in bash, or `limit' in csh...  MAXUPRC
is only the default.  CHILD_MAX shouldn't be defined because the limit
isn't constant.

>> In FreeBSD 2.1 you can increase this limit runtime with 
>> 	sysctl kern.maxprocperuid

sysctl is easier to use than *limit, but less flexible.

Bruce