This is the mail archive of the
mailing list for the Cygwin project.
RE: bash and CSRSS consuming 100% of CPU
- From: "Charli Li" <KBarticle889459 at aim dot com>
- To: <cygwin at cygwin dot com>
- Date: Mon, 19 Jun 2006 13:43:37 -0400
- Subject: RE: bash and CSRSS consuming 100% of CPU
-----BEGIN PGP SIGNED MESSAGE-----
- -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com]On Behalf
> Of Christopher Faylor
> Sent: Monday, June 19, 2006 12:32 PM
> To: firstname.lastname@example.org
> Subject: Re: bash and CSRSS consuming 100% of CPU
> On Mon, Jun 19, 2006 at 05:28:04PM +0100, Dave Korn wrote:
> >On 19 June 2006 17:13, email@example.com 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 220.127.116.111 and scan engine 18.104.22.168. I run this at least once a
> >> week and I keep the virus definition file up-to-date (currently have
> >> version 6/14/2006 rev. 35). I also run (at least once a week)
> Webroot Spy
> >> Sweeper, Program Version 4.5.3 (Build 560) with spyware
> definitions v 701,
> >> last updated 6/16/06. I ran both of these Friday night on the affected
> >> machine, and it came up clean.
> > 10 to 1 it's Symantec doing it. Can you thoroughly disable it and try
> OTOH, it is probably this:
> Cygwin DLL version info:
> DLL version: 1.5.19
> DLL epoch: 19
> DLL bad signal mask: 19005
> DLL old termios: 5
> DLL malloc env: 28
> API major: 0
> API minor: 150
> Shared data: 4
> DLL identifier: cygwin1
> Mount registry: 2
> Cygnus registry name: Cygnus Solutions
> Cygwin registry name: Cygwin
> Program options name: Program Options
> Cygwin mount registry name: mounts v2
> Cygdrive flags: cygdrive flags
> Cygdrive prefix: cygdrive prefix
> Cygdrive default prefix:
> Build date: Fri Jan 20 13:28:43 EST 2006
> CVS tag: cr-0x5ef
> Shared id: cygwin1S4
> i.e., this isn't a snapshot version of the DLL.
> Is it possible that the OP transferred things into, e.g.,
> rather than c:\cygwin\bin?
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 >...
>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 using it.
>Somebody else mentioned Windows Update. The affected machine is on
automatic Windows Update. In fact, I have a list of
>Microsoft updates that have come in recently but cannot be installed for
some arcane reason. I have not resolved this
>problem yet, and this is the first time I have ever had trouble installing
MS updates. Don't know whether this is related
>to the cygwin bash & CSRSS problem, but the coincidence is interesting.
>Now I see Dave Korn's suggestion about disabling Symantec. I'll look into
>- -- Joe
I don't think that I have ever suggested this, but here goes.
In my case, I formerly used bash, but after I changed some things, I got
Cygwin to work in the Z-Shell. Note that it doesn't invoke sh, just like
bash does. Edit the part in cygwin.bat that reads:
bash --login -i
(That can also be bash -l -i)
and change that to:
zsh -l -i
Cygwin will now start up in the Z-Shell with those modifications.
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 has been reported against pdksh (ksh). No
problems that I know of have been reported against ash, tcsh, or zsh.
And yes, please disable Symantec, as Dave said, since security
suites/products are a pain in the neck for Cygwin!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Cygwin)
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html