Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: 23 Jul 2001 16:55:36 -0400
Message-ID: <20010723205536.20378.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Still seeing fork failures on NT/2000 with current CVS repository
Note-from-DJ: This may be spam

I get this on Windows NT and Windows 2000 when a "#!/bin/sh" script
(i.e., an ash script, I believe) tries to run "rsync -a --delete
/u/jik/metal/ /scratch/jik/curl/":

      0 [main] rsync 832 open_stackdumpfile: Dumping stack trace to rsync.exe.stackdump
      0 [main] rsync 812 sync_with_child: child 832(0x290) died before initialization with status code 0xA011000
    893 [main] rsync 812 sync_with_child: *** child state child loading dlls
fork: Resource temporarily unavailable

Interestingly enough, when I run the same script with "bash <script>"
instead of "sh <script>", it works.

I got the impression from reading recent cygwin-developers messages
that these problems are supposed to be fixed, but perhaps I
misunderstood.

Does this ring enough bells with anyone, or do you need more info
(e.g., a strace log or stack trace) to figure out what's going wrong
here?

Thanks,

  jik