From owner-freebsd-hackers Thu Oct 23 06:54:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA27140 for hackers-outgoing; Thu, 23 Oct 1997 06:54:54 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from cs.iastate.edu (root@cs.iastate.edu [129.186.3.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA27135 for ; Thu, 23 Oct 1997 06:54:51 -0700 (PDT) (envelope-from ghelmer@cs.iastate.edu) Received: from popeye.cs.iastate.edu (popeye.cs.iastate.edu [129.186.3.4]) by cs.iastate.edu (8.8.7/8.8.7) with ESMTP id IAA02676; Thu, 23 Oct 1997 08:54:47 -0500 (CDT) Received: from localhost (ghelmer@localhost) by popeye.cs.iastate.edu (8.8.7/8.7.1) with SMTP id IAA07091; Thu, 23 Oct 1997 08:54:46 -0500 (CDT) X-Authentication-Warning: popeye.cs.iastate.edu: ghelmer owned process doing -bs Date: Thu, 23 Oct 1997 08:54:44 -0500 (CDT) From: Guy Helmer To: Charles Henrich cc: freebsd-hackers@FreeBSD.ORG Subject: Re: CHILD_MAX no longer valid in 2.2.5-RELEASE? In-Reply-To: <19971023030651.02177@crh.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 23 Oct 1997, Charles Henrich wrote: > I've send CHILD_MAX to 512 on my news server, which (used) to have the effect > of making the default maximum procs set to 512.. Bonus. Under 2.2.5-RELEASE > it doesnt appear to be having any effect :( The only thing I can think of is, > its placement in the config file is order important, or its no longer > supported? If the latter, how do you effect the same change in 2.2.5? init uses the "daemon" entry in /etc/login.conf to set process resource limits before executing /etc/rc; it appears to me that the "maxproc" entry (maxproc=256) is the one you need to adjust (see also login.conf(5) and getcap(3)). Hope that solves your problem, Guy Guy Helmer, Computer Science Graduate Student - ghelmer@cs.iastate.edu Iowa State University http://www.cs.iastate.edu/~ghelmer Research Assistant, Scalable Computing Laboratory, Ames Laboratory