Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: A process can't have more than 63 child processes.
References:	<s1sofwd7dq0 DOT fsf AT jaist DOT ac DOT jp> <20010208090337 DOT A29571 AT redhat DOT com>
Mime-Version:	1.0 (generated by tm-edit 7.106)
From:	Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
Date:	09 Feb 2001 09:12:49 +0900
In-Reply-To:	Christopher Faylor's message of Thu, 8 Feb 2001 09:03:37 -0500
Message-ID:	<s1sitmk7lz2.fsf@jaist.ac.jp>
Lines:	16
X-Mailer:	Gnus v5.3/Emacs 19.34

>>> On Thu, 8 Feb 2001 09:03:37 -0500
>>> Christopher Faylor <cgf AT redhat DOT com> said:

> I guess we should set PSIZE to 64.

Almost all applications don't practically need to have more
children than 64, so setting the limit to 64 probably causes no
problem. (I found this problem as I was trying `lmbench' which
isn't an ordinary application.)

Anyway, fork() should report the error of too many children to
applications. I believe it is practically important.
____
  | AIST      Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
  | HOKURIKU  School of Information Science
o_/ 1990      Japan Advanced Institute of Science and Technology

- Raw text -