Date: Thu, 23 Oct 1997 10:33:26 -0500 (CDT) From: Guy Helmer <ghelmer@cs.iastate.edu> To: Charles Henrich <henrich@crh.cl.msu.edu> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: CHILD_MAX no longer valid in 2.2.5-RELEASE? Message-ID: <Pine.HPP.3.96.971023101746.2752E-100000@popeye.cs.iastate.edu> In-Reply-To: <19971023104527.34841@crh.cl.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 23 Oct 1997, Charles Henrich wrote: > On the subject of Re: CHILD_MAX no longer valid in 2.2.5-RELEASE?, Guy Helmer stated: > > 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)). > > 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 :) login.conf's primary use is for defining authentication methods, setting user resource limits, and setting useful system-wide defaults at login time, based on user class, but it is marginally overloaded (in particular, for init(8) like we've noted). There ought to be a couple of pointers to this use of the daemon entry in login.conf in init(8)'s man page and LINT (assuming CHILD_MAX stays in) -- I suppose that means I ought to make diffs and write a gnats report :-) 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.HPP.3.96.971023101746.2752E-100000>