X-Spam-Check-By:	sourceware.org
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Cygrunsrv.exe 100% processor load
Date:	Thu, 4 May 2006 14:48:09 +0100
Message-ID:	<009201c66f81$612e0cb0$a501a8c0@CAM.ARTIMI.COM>
MIME-Version:	1.0
X-Mailer:	Microsoft Office Outlook 11
In-Reply-To:	<387481421.20060504101848@software-braun.de>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On 04 May 2006 09:19, Thomas Braun wrote:

> I'm running cygwin on a W2K server with all the current service packs
> and patches, and I'm experiencing intermittent CPU hogging by
> cygrunsrv.exe.

> I'm not sure *what* exactly triggers this, but one way to reproduce
> this is to use process explorer from www.sysinternals.com and try to
> show the process properties for cygrunsrv.exe.
> 
> This does not only bring process explorer to a halt, but also raises
> the CPU load from cygrunsrv.exe to between 60 and 100%

> I know this issue has been discussed here recently:
> 
> http://sourceware.org/ml/cygwin/2006-04/msg00240.html
> http://sourceware.org/ml/cygwin/2006-03/msg00337.html
> 
> ...but as far as I can see there is no real solution.

  Well, there probably is in this case.  What you need to do is find out
/which/ other process is injecting remote threads into the cygwin sshd
process.  It could be something security related like pfw or av s/w, or it
could as someone suggested recently be a windows update interaction.

  Now in theory (because I've not tried this myself yet) it should be possible
to find what process is doing this to your sshd/cygrunsrv, and by setting ACLs
on the service process deny access to whichever foreign process is messing it
up.  That ought to work, but there could be unforeseen problems if it ends up
turning out to be the case that you need to deny access to SYSTEM - you might
end up not being able to send control messages to the service perhaps, or
experience other odd effects.  But it's definitely worth a try.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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