From owner-freebsd-questions Sat Sep 16 12:38:57 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA03184 for questions-outgoing; Sat, 16 Sep 1995 12:38:57 -0700 Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA03176 for ; Sat, 16 Sep 1995 12:38:54 -0700 Received: by haven.uniserve.com id <30743>; Sat, 16 Sep 1995 12:40:37 +0100 Date: Sat, 16 Sep 1995 12:40:34 -0700 (PDT) From: Tom Samplonius To: Guido van Rooij cc: questions@freebsd.org Subject: Re: "limit maxprocs" vs. "sysctl kern.maxprocperuid" In-Reply-To: <199509161848.UAA00513@gvr.win.tue.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org Precedence: bulk On Sat, 16 Sep 1995, Guido van Rooij wrote: > Tom Samplonius wrote: > > > > What is the exact relationship between csh's "limit maxproc" and > > "sysctl kern.maxprocperuid"? > > Limit maxproc is valid only for the current process and all of its children. > > The other one is global and effective immediately for *all* uids. I tested the effects of "limit maxproc X", and it is most definitely affects other processes. For example, I logged in twice to two different virtual consoles, then I proceeded to run my limit (default is 40) of processes (for testing I used 'sleep 40') on one console. After that, I could not run any processes on the second console, until some processes running on the first console ended. How does one set the default "limit maxproc" value for all users? Tom