Date: Tue, 28 May 1996 08:05:27 -0400 (EDT) From: "matthew c. mead" <mmead@Glock.COM> To: michaelv@HeadCandy.com (Michael L. VanLoon -- HeadCandy.com) Cc: hackers@FreeBSD.org Subject: Re: CHILD_MAX Message-ID: <199605281205.IAA11478@Glock.COM> In-Reply-To: <199605280449.VAA04627@MindBender.HeadCandy.com> from "Michael L. VanLoon -- HeadCandy.com" at May 27, 96 09:49:53 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Michael L. VanLoon -- HeadCandy.com writes: > > Does anyone know why CHILD_MAX for the kernel and CHILD_MAX > >in the /usr/include/sys/syslimits.h are different (128 and 40 > >respectively)? I'm running into the problem of having too few > >processes available. If I redefine the define in syslimits.h to > >128 will I be able to run right away, or am I correct in > >presuming that I'm going to have to rebuild things? What all > >will I have to rebuild? > If you're running tcsh, you can just use the... > limit maxproc 128 > or > unlimit > ... commands. (Unlimit, of course, sets it to its maximum value -- > 1044 on my machine.) > Other shells can do the same thing with similar commands. I use zsh, and I run unlimit - in fact I checked the processes limit and it's "unlimited." I'm still getting stopped after 40. Maybe it uses CHILD_MAX. -matt -- Matthew C. Mead mmead@Glock.COM http://www.goof.com/~mmead/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605281205.IAA11478>