From: <sten.kristian.ivarsson@gmail.com>
To: <cygwin@cygwin.com>
Subject: Limit for number of child processes
Date: Wed, 26 Aug 2020 14:00:50 +0200 [thread overview]
Message-ID: <000401d67ba0$8b1f33b0$a15d9b10$@gmail.com> (raw)
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
next reply other threads:[~2020-08-26 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 12:00 sten.kristian.ivarsson [this message]
2020-08-26 17:57 ` Corinna Vinschen
2020-08-27 12:17 ` Sv: " sten.kristian.ivarsson
2020-08-28 1:42 ` Ken Brown
2020-08-28 8:35 ` Corinna Vinschen
2020-08-28 8:38 ` Sv: " sten.kristian.ivarsson
2020-08-28 12:29 ` Ken Brown
2020-08-28 13:36 ` Corinna Vinschen
2020-08-28 14:09 ` Sv: " sten.kristian.ivarsson
2020-08-28 16:02 ` Ken Brown
2020-08-28 17:39 ` Corinna Vinschen
2020-08-29 10:01 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000401d67ba0$8b1f33b0$a15d9b10$@gmail.com' \
--to=sten.kristian.ivarsson@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).