Date: Thu, 13 Jul 2000 22:44:45 -0700 From: "Brian O'Shea" <boshea@ricochet.net> To: clefevre@citeweb.net Cc: Narvi <narvi@haldjas.folklore.ee>, core-ix@hushmail.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Some proposals to FreeBSD kernel Message-ID: <20000713224445.S351@beastie.localdomain> In-Reply-To: <puologd2.fsf@pc166.gits.fr>; from Cyrille Lefevre on Mon, Jul 10, 2000 at 10:55:05PM %2B0200 References: <Pine.BSF.3.96.1000710165917.36592D-100000@haldjas.folklore.ee> <puologd2.fsf@pc166.gits.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 10, 2000 at 10:55:05PM +0200, Cyrille Lefevre wrote: > ... an idea would be to add some limit to limit the number of processes > forked by a process (at one time in addition to the number of processes > by user which may be relative to the system wide limit > (maxprocperproc=nproc-10)... Actually this wouldn't solve your problem since the processes created are not all children of the first process that you start. Every child process also executes fork() in a loop, so when one reaches its per- process limit, all of its children will also be able to create up to their limit of child processes, each child of which will do the same, ad infinitum (well, until maxproc is reached and you can't create any more processes and your system is wedged again). The kern.maxprocperuid sysctl addresses this problem better. -brian -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000713224445.S351>