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

Reply via email to