From: "A. Doggy" <techpro2004@gmail.com>
To: cygwin@cygwin.com
Subject: Re: sshd high cpu load
Date: Thu, 27 May 2021 07:51:40 -0400 [thread overview]
Message-ID: <d5925963-d570-72d0-2da4-9946361545d5@gmail.com> (raw)
In-Reply-To: <908a746f-dd54-775b-7dfd-27e453d1a6da@gmail.com>
On 5/25/2021 8:23 PM, A. Doggy wrote:
>
> On 5/20/2021 9:31 PM, A. Doggy wrote:
>> To cygwin.
>>
>>
>> A Little more info: I actually have 1 client that connects regularly
>> to the server. That client uses a program called goodsync. When I
>> block goodsync from connecting, the problem goes away and I only have
>> 1 sshd.exe process running. When I unblock goodsync, I have multiple
>> sshd.exe processes running and my cpu gets maxed out. Please test it
>> like this. Thanks.
>>
>> On 5/20/2021 12:02 PM, A. Doggy wrote:
>>> Anyone?
>>>
>>> On 5/19/2021 12:48 AM, A. Doggy wrote:
>>>> To Cygwin,
>>>>
>>>>
>>>> I am running cygwin openssh as a windows service. I have been doing
>>>> so for many years with out issue. Recently, I have been running
>>>> into an issue where it maxes out my cpu on any version newer than
>>>> 8.4p1-1. The solution is to downgrade to 8.4p1-1. My server machine
>>>> is a dell t330 running windows 10. I am not a business despite
>>>> using business grade hardware.I have tried both 20h2 and 21h1 but
>>>> no luck. There are no users signed in when the issues occur and
>>>> occurs within minutes of booting up. The only change from the
>>>> default config is I have it running on a nonstandard port. Any
>>>> advice is welcome as I really would like to upgrade to a newer
>>>> version. Thanks
>>>>
>
>
>
> To Cygwin,
>
>
> I remember seeing someone was going to work on this on Sunday. I am
> checking if this is resolved for other users as I do not want to
> update and be stuck. Thanks.
>
bump
To Cygwin,
I remember seeing someone was going to work on this on Sunday. I am
checking if this is resolved for other users as I do not want to update
and be stuck. Thanks.
next prev parent reply other threads:[~2021-05-27 11:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 4:48 A. Doggy
2021-05-20 16:02 ` A. Doggy
2021-05-20 16:10 ` [cygwin] " Jason Pyeron
2021-05-20 18:48 ` EXTERNAL: " Wells, Roger K.
2021-05-20 20:33 ` Andrey Repin
2021-05-20 23:12 ` [cygwin] " Jason Pyeron
2021-05-21 12:54 ` Wells, Roger K.
2021-05-21 1:31 ` A. Doggy
2021-05-22 15:52 ` Andrey Repin
2021-05-26 0:23 ` A. Doggy
2021-05-27 11:51 ` A. Doggy [this message]
2021-05-28 23:06 ` A. Doggy
2021-05-28 23:44 ` A. Doggy
2021-05-30 16:41 A. Doggy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5925963-d570-72d0-2da4-9946361545d5@gmail.com \
--to=techpro2004@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).