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
From: ericblake AT comcast DOT net (Eric Blake)
To: Cygwin List <cygwin AT cygwin DOT com>
Subject: Windows update vs. cygrunsrv
Date: Wed, 12 Oct 2005 15:45:44 +0000
Message-Id: <101220051545.21471.434D2FA800096FCD000053DF22007613940A050E040D0C079D0A@comcast.net>

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.

--
Eric Blake

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