DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A00333851C1C
To: <cygwin@cygwin.com>
Subject: Limit for number of child processes
Date: Wed, 26 Aug 2020 14:00:50 +0200
Message-ID: <000401d67ba0$8b1f33b0$a15d9b10$@gmail.com>
MIME-Version: 1.0
Thread-Index: AdZ7oDrfzUXMB3MfSQKEXK7fWVb4oA==
Content-Language: en-gb
From: Kristian Ivarsson via Cygwin <cygwin@cygwin.com>
Reply-To: sten.kristian.ivarsson@gmail.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

Dear cygwin folks

It seems like there's a limit of the number of possible child processes
defined to 256 with 'NPROCS' in //winsup/cygwin/child_info.h used in
'cprocs' in //winsup/cygwin/sigproc.cc

256 is quite few possible children in an enterprise environment and perhaps
the limit should be limited by the physical resources or possibly Windows ?

As of now, posix_spawnp sometimes fail with EAGAIN (maybe it should be
ENOMEM ?) if this limit is reached

Would it be possible to somehow make this dynamic and let the operating
system set the limits ?


Best regards,
Kristian

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple