From owner-freebsd-hackers Mon Feb 27 11:25:46 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA03191 for hackers-outgoing; Mon, 27 Feb 1995 11:25:46 -0800 Received: from alpha.dsu.edu (ghelmer@alpha.dsu.edu [138.247.32.12]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA03185 for ; Mon, 27 Feb 1995 11:25:45 -0800 Received: (from ghelmer@localhost) by alpha.dsu.edu (8.6.10/8.6.10) id NAA00655; Mon, 27 Feb 1995 13:24:41 -0600 Date: Mon, 27 Feb 1995 13:24:40 -0600 (CST) From: Guy Helmer To: Guido van Rooij cc: freebsd-hackers@freefall.cdrom.com Subject: Re: Max procs per user In-Reply-To: <199502271858.TAA03863@gvr.win.tue.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk On Mon, 27 Feb 1995, Guido van Rooij wrote: > Guy Helmer wrote: > > Is there a common way of increasing the max processess allowed per user > > in FreeBSD 1.1.5.1? Is it "options MAXUPRC" in the kernel configuration > > file? > > You could recomfigure uoru kernel with a higher 'maxusers' setting. > If you dont want that, look in /sys/conf/param.c for NPROC or such. > Determijne the new value and put options NPROC="blah" in your kernel > config. I neglected to mention that the kernel has been configured with "maxusers 128", which I assumed would create a vastly sufficient number of processes for the entire system (2068, according to the formula in param.c for this 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? > In FreeBSD 2.1 you can increase this limit runtime with > sysctl kern.maxprocperuid That will be nice! > -Guido Guy Helmer, Dakota State University Computing Services - ghelmer@alpha.dsu.edu