Date: Mon, 27 May 1996 21:49:53 -0700 From: "Michael L. VanLoon -- HeadCandy.com" <michaelv@HeadCandy.com> To: "matthew c. mead" <mmead@glock.com> Cc: hackers@freebsd.org Subject: Re: CHILD_MAX Message-ID: <199605280449.VAA04627@MindBender.HeadCandy.com> In-Reply-To: Your message of Mon, 27 May 96 11:22:31 -0400. <199605271522.LAA05548@Glock.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.
-----------------------------------------------------------------------------
Michael L. VanLoon michaelv@HeadCandy.com
--< Free your mind and your machine -- NetBSD free un*x >--
NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3,
Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32...
NetBSD ports in progress: PICA, others...
Roll your own Internet access -- Seattle People's Internet cooperative.
If you're in the Seattle area, ask me how.
-----------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605280449.VAA04627>