On Tue, 20 Jun 2006, Science Guy wrote:
> From message http://cygwin.com/ml/cygwin/2006-06/msg00534.html:
>
> > Dave, I think you missed this:
> >
> >>sciguy wrote:
> >>>I am networked to a Linux machine, so I moved the tar file
> >>>cygwin-inst-20060614.tar.bz2 over to the Linux machine, created
>From message http://cygwin.com/ml/cygwin/2006-06/msg00534.html:
> Dave, I think you missed this:
>
>>sciguy wrote:
>>>I am networked to a Linux machine, so I moved the tar file
>>>cygwin-inst-20060614.tar.bz2 over to the Linux machine, created a dummy
>>>cygwin directory to hold the file, and un-
On Tue, Jun 20, 2006 at 12:57:54PM +0100, Dave Korn wrote:
>On 20 June 2006 02:11, Science Guy wrote:
>
>> I got cygwin working once again on my problem machine. (Hooray!)
>>
>> The problem was that the snapshot tar file, cygwin-inst-20060614.tar.bz2,
>> had cygwin1.dll in /usr/bin but failed to
On 20 June 2006 02:11, Science Guy wrote:
> I got cygwin working once again on my problem machine. (Hooray!)
>
> The problem was that the snapshot tar file, cygwin-inst-20060614.tar.bz2,
> had cygwin1.dll in /usr/bin but failed to replace the old cygwin1.dll in
> /bin. I copied over the new cyg
I got cygwin working once again on my problem machine. (Hooray!)
The problem was that the snapshot tar file, cygwin-inst-20060614.tar.bz2,
had cygwin1.dll in /usr/bin but failed to replace the old cygwin1.dll in
/bin. I copied over the new cygwin1.dll into /bin, and things are working
nicely onc
On 19 June 2006 18:44, Charli Li wrote:
> The reason for the Z-Shell, if Dave, cgf, or Corinna is asking, is because
> bash may be a little buggy. The only problem that I know of (yours) is
> reported against bash (perhaps anybody would like to reference more bash
> problems???), and a problem ha
ne 19, 2006 12:32 PM
>> To: cygwinXXXXXXXXXXX
>> Subject: Re: bash and CSRSS consuming 100% of CPU
>
>Science Guy then writes:
>>Hey, my message, which I had been trying to post since early Saturday
>>morning, finally made it through. That was a struggle >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of Christopher Faylor
> Sent: Monday, June 19, 2006 12:32 PM
> To: cygwin@cygwin.com
> Subject: Re: bash and CSRSS consuming 100% of CPU
>
Hey, my message, which I had been trying to post since early Saturday morning,
finally made it through. That was a struggle ...
To answer some issues that have come up since then, Linda Walsh asked about
"procexp" (Process Explorer). Since I never heard of this program, I assume I
am not usin
On Mon, Jun 19, 2006 at 05:28:04PM +0100, Dave Korn wrote:
>On 19 June 2006 17:13, [EMAIL PROTECTED] wrote:
>
>> p.s. To answer Brett's question: Yes, I am running virus and spyware
>> protection software. I run Symantec AntiVirus Corporate Edition, Program
>> version 8.0.1.501 and scan engine 4
On 19 June 2006 17:13, [EMAIL PROTECTED] wrote:
> p.s. To answer Brett's question: Yes, I am running virus and spyware
> protection software. I run Symantec AntiVirus Corporate Edition, Program
> version 8.0.1.501 and scan engine 4.1.0.22. I run this at least once a
> week and I keep the virus
Thanks to several people for the "snapshot" suggestions. I tried installing a
new snapshot but, unfortunately, that did not fix the problem. Here's what I
did. Maybe somebody can tell me whether I did something wrong.
I tried running this tar in a bash window on the affected machine:
$ /b
On Sun, Jun 18, 2006 at 03:18:13PM -0700, Brian Dessent wrote:
>Linda Walsh wrote:
>>I didn't see Science Guy mention procexp? Um, hey, S.G., are you using
>>Process Explorer?
>
>There are probably other programs that use the same technique and cause
>the same effect, like windows update.
>
>>I re
Linda Walsh wrote:
> I didn't see Science Guy mention procexp? Um, hey, S.G.,
> are you using Process Explorer?
There are probably other programs that use the same technique and cause
the same effect, like windows update.
> I remember the ProcExp bug, but it only happened when I tried t
Brian Dessent wrote:
Science Guy wrote:
This problem has been noted before by someone else,
http://www.mail-archive.com/cygwin@cygwin.com/msg37532.html
but I followed the threads and can find no resolution.
When I fire-up a cygwin bash window, everything is fine for a few minutes.
On Fri, Jun 16, 2006 at 06:58:58AM -0600, Eric Blake wrote:
>According to Science Guy on 6/16/2006 6:55 AM:
>>Thanks for the suggestion, Brian. Unfortunately, it did not help the
>>problem at all.
>>
>>I am not 100% sure what you meant by "try a snapshot," but I am
>>guessing that you meant simply
When I fire-up a cygwin bash window, everything is fine for a few minutes.
Then the CPU utilization on my system suddenly jumps to 100%. Bash is
typically grabbing about 80% of the CPU, with almost all the rest grabbed by
Are you running any virus or spyware protection software?
Brett
--
Un
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Science Guy on 6/16/2006 6:55 AM:
> Thanks for the suggestion, Brian. Unfortunately, it did not help the
> problem at all.
>
> I am not 100% sure what you meant by "try a snapshot," but I am guessing
> that you meant simply to reinstall
Thanks for the suggestion, Brian. Unfortunately, it did not help the
problem at all.
I am not 100% sure what you meant by "try a snapshot," but I am guessing
that you meant simply to reinstall cygwin. So I did that, again. Last
night I renamed the old cygwin directory from C:\cygwin to C:\cygwi
Science Guy wrote:
>
> This problem has been noted before by someone else,
>
> http://www.mail-archive.com/cygwin@cygwin.com/msg37532.html
>
> but I followed the threads and can find no resolution.
The problem is caused by sysinternals' process explorer injecting its
own threads into other proc
20 matches
Mail list logo
