From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from forward102o.mail.yandex.net (forward102o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::602]) by sourceware.org (Postfix) with ESMTPS id 872D3394342A for ; Sun, 18 Apr 2021 14:20:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 872D3394342A Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=yandex.ru Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=anrdaemon@yandex.ru Received: from myt3-f110b7494aff.qloud-c.yandex.net (myt3-f110b7494aff.qloud-c.yandex.net [IPv6:2a02:6b8:c12:693:0:640:f110:b749]) by forward102o.mail.yandex.net (Yandex) with ESMTP id 75F136680EF6; Sun, 18 Apr 2021 17:20:02 +0300 (MSK) Received: from myt5-aad1beefab42.qloud-c.yandex.net (myt5-aad1beefab42.qloud-c.yandex.net [2a02:6b8:c12:128:0:640:aad1:beef]) by myt3-f110b7494aff.qloud-c.yandex.net (mxback/Yandex) with ESMTP id cV9IBsAycj-K2IStxX6; Sun, 18 Apr 2021 17:20:02 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1618755602; bh=cbQ9RPt5lgUyETkgJTMitDbN+DXEkTc2SJEywuZ7l90=; h=In-Reply-To:Subject:To:From:Message-ID:References:Date:Reply-To; b=Vre1770VF0nA3OFJ61Ej86M9HN0CNhwG6GS1etA1fz8Ljn+sfjAXuDfo1hkxaNIuW S06Xkze4eOR4iPGhnorwEuJoQ5Sfo23nec/hkYOHR73JoXub+p8eJNnhmYzoQGMeRW 1bNExFwyNhCeD8ote1ZQaWMf8CEAzojQvdsqF3j0= Authentication-Results: myt3-f110b7494aff.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru Received: by myt5-aad1beefab42.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id 23pi1P899Q-K1KKPu4g; Sun, 18 Apr 2021 17:20:01 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Sun, 18 Apr 2021 14:07:23 -0000 Date: Sun, 18 Apr 2021 17:07:23 +0300 From: Andrey Repin X-Mailer: The Bat! (v6.8.8) Home Reply-To: cygwin@cygwin.com X-Priority: 3 (Normal) Message-ID: <391666392.20210418170723@yandex.ru> To: iw875421@gmx.eu, cygwin@cygwin.com Subject: Re: sshd 100% Load after disconnect In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_THEBAT, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Apr 2021 14:20:06 -0000 Greetings, iw875421@gmx.eu! > sshd seems to run at 100% Load for one thread after ssh disconnect 125% or more, actually. > (Close Terminal Window) on my Windows 10 computer. > If I use exit it isn't so. > I have to kill sshd or reboot the machine to kill the load. Kill the shell (or another process that's holding it). It's safer a little. -- With best regards, Andrey Repin Sunday, April 18, 2021 17:06:24 Sorry for my terrible english...