delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT sources DOT redhat DOT com |
Delivered-To: | mailing list cygwin AT sources DOT redhat DOT com |
Reply-To: | <jej AT 6pine DOT com> |
From: | "J. Eric Josephson" <jej AT 6pine DOT com> |
To: | "cygwin" <cygwin AT cygwin DOT com> |
Subject: | BASH and CPU use..... |
Date: | Fri, 9 Mar 2001 19:52:51 -0500 |
Message-ID: | <NDBBINGNIKAODLECKNBKGELODGAA.jej@6pine.com> |
MIME-Version: | 1.0 |
X-Priority: | 3 (Normal) |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.50.4133.2400 |
Importance: | Normal |
I been looking through the list archives and have seen a number of postings on this subject. I have not seen a resolution, so I'm assuming that it's still a bit on the elusive side. Here is my 2 bits.... I have noticed it with the past few versions of bash.exe and cygwin1.dll I am currently running the full 1.1.8 distribution from January 2001. While I cannot get the problem to happen on demand, I'm close enough. It takes me about 3 or 4 minutes. Here is what I'm doing to make it happen: OS: win 2k Pro or Server (happens on both with and w/o sp1) I've written and simple but busy script that is intended to loop forever with a 2 second sleep between cycles. It does lots of file touching and compiling lists of PIDs in files. It also does some script spawning and killing. If I let it run for a while and then touch a semaphore into place that tells the script to spawn a child or two, then have it kill the child scripts and launch new ones, etc... after a couple of cycles of this, the parent bash shell goes to 98%+ of the CPU and the bash shell is no longer operating properly at all. It requires me to close the cmd window to stop the script. Not that I'm looking for an immediate fix, but if someone that is a better coder than I is feeling like a challenge, here you go. I'd be happy to test the results and/or send my script to anybody that want to take a shot at it. -- J. Eric Josephson mailto:jej AT 6pine DOT com AIM: "jejosephso" -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |