Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 21 Mar 2003 21:44:54 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Cannot fork: Resource temporarily unavailable Message-ID: <20030322024454.GA22801@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030321203752 DOT 45196 DOT qmail AT web10006 DOT mail DOT yahoo DOT com> <20030322023245 DOT GA3044 AT Orlyn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030322023245.GA3044@Orlyn> User-Agent: Mutt/1.5.1i On Sat, Mar 22, 2003 at 03:32:45AM +0100, Luc Hermitte wrote: >May be our PID numbers consumption is going very fast because we have >some "resident" programs like anti-viruses, firewalls, etc. But the >problem still remains: there is a limit that stop us from using cygwin >to accomplish more or less critical things like recompiling some >programs. No one is denying that. However, rather than having people spelunking for other reports of the problem, it might be useful if someone with programming experience who had the problem actually tried *debugging* it. If you are using cygwin to recompile some programs maybe cygwin should be one of those programs and maybe you ought to try tracking the problem down yourself. There are something like 200+K lines of code in cygwin and probably something like three people actively hacking on it. So, realistically speaking, the way to fix problems is often to debug the problem yourself. That is assuming that people aren't just having fun finding old reports of the same problem and actually want to solve the problem. cgf -- 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/