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
To: cygwin AT cygwin DOT com
From: Rolf Campbell <thats DOT unpossible AT gmail DOT com>
Subject:  Re: Windows update vs. cygrunsrv
Date:  Wed, 12 Oct 2005 12:30:24 -0400
Lines: 26
Message-ID: <dijdn0$m4h$1@sea.gmane.org>
References:  <101220051545 DOT 21471 DOT 434D2FA800096FCD000053DF22007613940A050E040D0C079D0A AT comcast DOT net>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 1.4.1 (Windows/20051006)
In-Reply-To: <101220051545.21471.434D2FA800096FCD000053DF22007613940A050E040D0C079D0A@comcast.net>
X-IsSubscribed: yes

Eric Blake wrote:
> I don't know it this was unique to my machine, but am
> reporting it in case anyone else runs into the same
> issue.  When running Microsoft update today, on Win2k,
> the patch for Security Update for DirectX 9 for Windows
> 2000 (KB904706) hung during installation, with an
> instance of cygrunsrv hogging 100% CPU, until I had
> stopped every last one of my cygrunsrv processes.  I
> don't know what the Microsoft update was trying to do
> to running services during the update, but it obviously
> didn't interact very well with cygrunsrv.
> 
> Anyways, since stopping everything allowed the installation
> to proceed, and the required reboot brought up a working
> system, I don't know if it is worth trying to patch cygrunsrv
> to behave nicer in the presence of whatever the Windows
> upgrade was throwing at it.  Rather, I'm just posting this
> as a sort of FYI for anyone else that might encounter the
> same behavior.

I updated 3 machines: 2 XP boxes an 1 Win2k box.  All 3 were running 
cygrunsrv and sshd.  I only experienced problems on the Win2k box. 
cygrunsrv hogged the cpu until I killed it, then sshd hogged the cpu 
until I killed it.  After killing those processes, the update proceeded 
without issue and after the restart everything (including ssh) was 
working fine.


--
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/