X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.5 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_NONE,TW_RX,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
X-Authority-Analysis:	v=1.0 c=1 a=DzkyhEnBTs8A:10 a=8nJEP1OIZ-IA:10 a=cTvFUKQJb3kQq0uE8P8A:9 a=A0jw8ynZbSTEN2I_DGd-Z0JyB_kA:4 a=wPNLvfGTeEIA:10 a=SQWScJox1rqPyTtK:21 a=MNHvYSDYbqUPjGfL:21
Message-ID:	<4C939E17.8030208@charter.net>
Date:	Fri, 17 Sep 2010 12:57:59 -0400
From:	SJ Wright <sjwright68 AT charter DOT net>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Unacceptable behavior -- slowing down script execution
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

Hi folks.

Through fits and starts, and with no more feedback from the list than 
Dave Korn's self-admitted "wild guess" about gcclib1 folders etc, my 
Cygwin is no longer shedding empty shell stack-dump files like dandruff. 
But certain things are continuing to alarm me. I'll put them in the form 
of questions and whoever knows the answers, please take the time to do so.

1. Is it normal behavior, once rxvt is launched, for cmd.exe to remain 
running as a process?
2. Using a batch-to-executable utility, I converted a customized 
rxvt-launching .bat file into an executable. Should this also stay open 
as a process in Task Manager once its work is done?
3. Is it normal behavior for one BASH script to spawn more than one 
subshell?
4. Is it normal for any script to run CPU usage up to 100%?

Regarding #4:
I have a script that I ran in GNOME Terminal less than an hour ago. I 
"time"d it -- the return was 20.6 seconds on the first line (real?). I 
ran the same script fifteen minutes later, evaluating identical files of 
the same type, length (5.37kb and 345b ASCII text) and time stamp, and 
after 7 minutes it was barely one-eighth complete. That's when I checked 
Task Manager and found my CPU usage was at 100% and three bash.exe's 
were running simultaneously. Admittedly the script calls on several 
externals, but considering the difference in completion times  -- I 
estimate that had I not interrupted the process with ctrl-c, the Cygwin 
run would have taken just under 40 minutes to finish -- _and the fact 
that it spawned an unusual number of subshells, it doesn't speak highly 
for Cygwin as a viable option or means for people to "keep their hand 
in" w/re their  Unix skill-sets.

5. Is this a bug peculiar to this version/build of Cygwin? I don't 
recall any such issues when running complicated scripts before 1.7.x.

Hoping someone can answer any or all of the foregoing.

Cheers, SJ Wright



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

- Raw text -