Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: 6 Sep 2001 12:47:56 -0400 Message-ID: <20010906164756.19885.qmail@lizard.curl.com> From: Jonathan Kamens To: cygwin-developers AT cygwin DOT com In-reply-to: <20010906142836.7323.qmail@lizard.curl.com> (message from Jonathan Kamens on 6 Sep 2001 10:28:36 -0400) Subject: Re: Figured out how to reproduce vfork/rsync bug! References: <20010906142836 DOT 7323 DOT qmail AT lizard DOT curl DOT com> Earlier, I wrote: > In particular, if you put this script into a file and run it: > > #!/bin/sh > > export 'INCLUDE=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' > rsync /tmp/foo/ /tmp/bar/ > > You'll get the Cygwin failure I've previously reported, I've subsequently discovered that that's wrong. The INCLUDE variable needs to be in your bash environment *before* ash spawns, or the bug doesn't happen. So put this in var.sh: export 'INCLUDE=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' Then put this in test.sh: #!/bin/sh mkdir -p /tmp/foo /tmp/bar rsync /tmp/foo/ /tmp/bar/ Then run in a bash window: . var.sh ./test.sh Corinna, could you try this and see what it does? jik