From owner-freebsd-hackers  Thu Oct 23 07:45:36 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id HAA00800
          for hackers-outgoing; Thu, 23 Oct 1997 07:45:36 -0700 (PDT)
          (envelope-from owner-freebsd-hackers)
Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA00790
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 23 Oct 1997 07:45:30 -0700 (PDT)
          (envelope-from henrich@crh.cl.msu.edu)
Received: (from henrich@localhost)
	by crh.cl.msu.edu (8.8.5/8.8.5) id KAA09776;
	Thu, 23 Oct 1997 10:45:27 -0400 (EDT)
Message-ID: <19971023104527.34841@crh.cl.msu.edu>
Date: Thu, 23 Oct 1997 10:45:27 -0400
From: Charles Henrich <henrich@crh.cl.msu.edu>
To: Guy Helmer <ghelmer@cs.iastate.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: CHILD_MAX no longer valid in 2.2.5-RELEASE?
References: <19971023030651.02177@crh.cl.msu.edu> <Pine.HPP.3.96.971023084622.2752D-100000@popeye.cs.iastate.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84
In-Reply-To: <Pine.HPP.3.96.971023084622.2752D-100000@popeye.cs.iastate.edu>; from Guy Helmer on Thu, Oct 23, 1997 at 08:54:44AM -0500
X-Operating-System: FreeBSD 2.2.2-RELEASE
X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF  76 C4 B8 C9 6E 41 A4 4F
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On the subject of Re: CHILD_MAX no longer valid in 2.2.5-RELEASE?, Guy Helmer stated:

> > 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

I'll give it a shot, thanks! Im wondering that perhaps the name login.conf is
a badly named file, especially if its more to do with userresources and
nothing to do with the login process.  Someone should also take CHILD_MAX out
of LINT :)

-Crh

       Charles Henrich     Michigan State University     henrich@msu.edu

                         http://pilot.msu.edu/~henrich