This is the mail archive of the
mailing list for the Cygwin project.
Re: fork: Resource temporarily unavailable
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 19 Oct 2006 16:39:42 -0400
- Subject: Re: fork: Resource temporarily unavailable
- References: <00dd01c6f3b5$18b7d9d0$2c1418ac@andydesktop>
- Reply-to: cygwin at cygwin dot com
Andy Hall wrote:
It seems that somewhere between cygwin 1.5.19-4 and 1.5.21-2 some change was
made that causes this error. I have a bash script that is used to create a
number of client processes that run in parallel and generate TCP/IP
conversations with a remote server being tested This script can configure
and run any number of these clients executing simultaneously. The clients
can be either .exe files based on .NET or a JVM (.exe) running a Java-based
client. These scripts run flawlessly on Linux or Solaris (java clients
only) or on a Win2K Professional box running cygwin 1.5.19-4 (both java or
.NET clients) They were also running flawlessly on a Win2K Server, until
it got upgraded to cygwin 188.8.131.52-2. After that, the scripts run for a
while until the message "fork: Resource temporarily unavailable" occurs, at
which point there are all sorts of bizarre and unexplainable failures. If
run for a reasonable amount of time these scripts will always result in this
The obvious question is, "How can we revert the Win2K Server back to cygwin
184.108.40.206.4 so that we can continue to run tests from this machine?
Alternatively, is there fix or patch available for this?
I have attached the output of cygcheck for both machines.
How does it run outside the terminal server?
Has the virus scanner been installed/updated on the server? How about
recently installed Logitech drivers? Both of these have been implicated
in fork-related failures. See the related thread in the last week:
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html