[PATCH] Cygwin: getdtablesize: always return OPEN_MAX_MAX

Corinna Vinschen corinna-cygwin@cygwin.com
Mon Feb 1 09:50:54 GMT 2021


On Jan 28 15:33, Ken Brown via Cygwin-patches wrote:
> On 1/28/2021 11:07 AM, Corinna Vinschen via Cygwin-patches wrote:
> > One problem is that there are some applications in the wild which run
> > loops up to either sysconf(_SC_OPEN_MAX) or OPEN_MAX to handle open
> > descriptors.  tcsh is one of them.  It may slow done tcsh quite a bit
> > if the loop runs to 3200 now every time.
> 
> I don't use tcsh.  Is it easy to test this?

I just checked the source.  In the olden days, before the invention of
close-on-exec, tcsh closed all descriptors > 2 up to OPEN_MAX prior to
starting any executable.

With close-on-exec this happens only at startup and after an error
occured.

So testing should be easy: The tcsh startup may be noticably slower.


Corinna


More information about the Cygwin-patches mailing list