-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://cygwin.com/acronyms/#PPIOSPE
According to Sarcar, Shourya C (GE Healthcare) on 10/27/2005 1:29 AM:
Now it looks like you have two copies of cygwin installed,
and that c:\insite\bin is still trying to compete with
c:\cygwin\bin. Cygwin does
Whoa! You are due for a big-time upgrade. Cygwin is at
1.5.18, bash at 3.0-11, coreutils at 5.3.0-9. Until you have
an up-to-date configuration (get one by rerunning setup.exe),
this list won't be of much help to you.
Hi Eric,
I upgraded my system, but I am still seeing the CPU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Sarcar, Shourya C (GE Healthcare) on 10/26/2005 2:34 AM:
I upgraded my system, but I am still seeing the CPU usage issue.
Now it looks like you have two copies of cygwin installed, and that
c:\insite\bin is still trying to compete with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Urgh - http://cygwin.com/acronyms/#TOFU - reformatted.
-Original Message-
From: Eric Blake [mailto:[EMAIL PROTECTED]
http://cygwin.com/acronyms/#PCYMTNQREAIYR
That message was for a much older configuration. Perhaps the issue has
been
Healthcare); cygwin@cygwin.com
Subject: Re: CPU usage issue with bash
Bash seems to be taking up a lot of CPU resources for me. It peaks to
100% for lengthy spans of around 20-30 seconds.
On NT systems (with an older cygwin) I notice peaks to around 70-80%
for shorter durations of time
Bash seems to be taking up a lot of CPU resources for me. It peaks to
100% for lengthy spans of around 20-30 seconds.
On NT systems (with an older cygwin) I notice peaks to around 70-80% for
shorter durations of time.
Is this a known issue with bash ?
I found this on the archives.
Bash seems to be taking up a lot of CPU resources for me. It peaks to
100% for lengthy spans of around 20-30 seconds.
On NT systems (with an older cygwin) I notice peaks to around 70-80% for
shorter durations of time.
Is this a known issue with bash ?
I found this on the archives.
7 matches
Mail list logo