X-Spam-Check-By:	sourceware.org
From:	sciguy AT comcast DOT net
To:	cygwin AT cygwin DOT com
Subject:	Re: bash and CSRSS consuming 100% of CPU
Date:	Mon, 19 Jun 2006 16:32:01 +0000
Message-Id:	<061920061632.26382.4496D1810004CE450000670E2200761394979A09070C9C@comcast.net>
X-Mailer:	AT&T Message Center Version 1 (Apr 11 2006)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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 that.  Thanks.

-- Joe

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -