public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "David Ryan" <oobles@hotmail.com>
To: <cygwin@cygwin.com>
Subject: Too many open files
Date: Tue, 12 Feb 2002 15:50:00 -0000	[thread overview]
Message-ID: <001701c1b41f$9e0d9280$0900a8c0@robot> (raw)


I attempted to find an answer to this online and in archives, but had no
success.  I have a large make file with thousands of files which failed at
the linking step.  On restarting the make after changing the link settings I
discovered the make file halted with "Too many open files".

I am running the latest version of cygwin 1.3.9 with all other tools updated
on a Windows 2000 (Build 2195: Service Pack 2) machine.  The files being ran
through in the makefile are on a Windows NT machine on a small network.  I
checked the NT machine network resources and found that over 2000 files were
open for read by the machine running make.  Even after make is finished the
files continue to stay open.  Even after closing cygwin.

Is this a problem in how make works?  Does cygwin keep file handles openned
and cached?  Anyone got any idea whats going on?  Anyone experienced the
same problem?

Thanks.
David.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2002-02-12 23:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12 15:50 David Ryan [this message]
2002-02-26 15:51 Kirk Erickson
2002-02-26 16:13 ` Larry Hall (RFK Partners, Inc)
2002-03-01 10:20   ` Kirk Erickson

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='001701c1b41f$9e0d9280$0900a8c0@robot' \
    --to=oobles@hotmail.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).