X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Steve <pooey66 AT sbcglobal DOT net>
Subject:	1.5.21 Forked background processes
Date:	Mon, 2 Oct 2006 19:59:13 +0000 (UTC)
Lines:	44
Message-ID:	<loom.20061002T215900-610@post.gmane.org>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Hello All,

When running as a background process, forking using `backtick` assignments
causes the process to die and leaves the forked process in a defunct state. This
seems like a sever problem with cygwin process handling and I was wandering if
anyone else in this group has ran into this.   

Here is an example that will reproduce the problem:


file1.sh:
-----------------------------------------------
#!/usr/bin/bash

./file2.sh &

------------------------------------------------

file2.sh
------------------------------------------------
#!/usr/bin/bash

while [ 1 ]
do
     val=`echo $val`
     val=$((val + 1))
     echo $val
done
------------------------------------------------


After running ./file1.sh, the background process will die very quickly
as seen with 'echo $val' (100 - 150) and leave the forked (backtick) process in
what appears to be in a defunct state. This will still appear as a
process, as seen with 'ps', even though it appears defunct ( check out
link /proc/≤pid>/cwd or file /proc/≤pid>/cmdline). This does not
happen if I remove the backtick assignment from file2.sh as well. 

I've posted this problem in the past and haven't recieved a response. I've seen
this with 1.5.19-4 and 1.5.20.

Thanks for any info,
->Steve



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -