This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

BASH and CPU use.....


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@6pine.com
AIM: "jejosephso"



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]