This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cygrunsrv.exe Processor Util 100% on Windows Server

2006/3/14, Brett Serkez <>:
> <snip>
> > I'm running sshd without the -r option all the time and I can't observer
> > the high CPU load as reported.  What's different on your system?!?
> I *believe* this primarily happens on Windows2000.  I wasn't able to
> track down.  The problem is that once the system gets in this state,
> with 100% CPU it is virtually unusable, the primary goal is to
> shutdown the daemon to get the system back for the primary user.
> This became such a problem that I finally ended up turning of the sshd
> daemon on all my Win2K systems and live without it, which was made
> possible by the introduction of systems running Fedora which I could
> use for secure access to the subnet.
> I haven't tried the latest release, I am due for maintenance with the
> impending Microsoft patch releases today, I'll turn it back on for
> some of the systems and see if I can reproduce.
> My general sense is that it has/had some thing to do with process
> creation and signal handling, perhaps a missed signal?!?!?

I have the same problem in W2K starting with at least with two cygwin
services, where one cygrunsrv.exe after some days goes up to 99%.
Killing the cygrunsrv.exe process alone is enough, which did
not affect the actual service, which runs fine even with the killed
service controller.
With one cygwin service alone I had no problem so far.
Regardless which service, if it's sshd, cron or cygserver.

No problem on the XP boxes.

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]