sshd high cpu load

[A. Doggy]

On 5/28/2021 7:06 PM, A. Doggy wrote:
>
> On 5/27/2021 7:51 AM, A. Doggy wrote:
>>
>> 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.
>
>
>
>
>
> double 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.
>


To Cygwin,


The problem still exits. Thanks.