This is the mail archive of the cygwin-developers@sources.redhat.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: A process can't have more than 63 child processes.

To: cygwin-developers at cygwin dot com
Subject: Re: A process can't have more than 63 child processes.
From: Kazuhiro Fujieda <fujieda at jaist dot ac dot jp>
Date: 09 Feb 2001 09:12:49 +0900
References: <s1sofwd7dq0.fsf@jaist.ac.jp> <20010208090337.A29571@redhat.com>

>>> On Thu, 8 Feb 2001 09:03:37 -0500
>>> Christopher Faylor <cgf@redhat.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@jaist.ac.jp>
  | HOKURIKU  School of Information Science
o_/ 1990      Japan Advanced Institute of Science and Technology

References:
- A process can't have more than 63 child processes.
  - From: Kazuhiro Fujieda
- Re: A process can't have more than 63 child processes.
  - From: Christopher Faylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]