X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=IpXsZCBSXZVirokZP1ZuiAIOa7Mvr
	qT8Vu/bopc9knvts2XOY3xfwKW6Wk2S33iAy9rK6HcvenUeeHBltqyJlzt84E2lj
	focHADw0Op5ZVw0YZfQ+si+TceafoFRhxOaQemIie6uCJCASF9D9idsOe3AgM8ep
	XrLsRoy6JQbXAY=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; s=default; bh=0GBqTTd4wEfoIQqIuHOFs1MxWRM=; b=vJZ
	nxlEbcS/Zwek9K99/vzNLpquXrUxaepwwtL/8tRgtAwF26XbpCB0b7fQ7FpWezA1
	C3li+/HaPRHCuXT1H9GmI9QLjOTIPWMkOdxOt2VzsX1+/jNtASdbsDcwfBp2CndQ
	RKeyci79Ewwl7Fgkpti4rUMW7/Z+sHPoBHzqpnVg=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-wi0-f172.google.com
MIME-Version:	1.0
X-Received:	by 10.194.59.43 with SMTP id w11mr3106487wjq.65.1397232476558; Fri, 11 Apr 2014 09:07:56 -0700 (PDT)
Date:	Fri, 11 Apr 2014 09:07:56 -0700
Message-ID:	<CA+jjjYRyY=PQjgqMOQj9qM146oM1q+VK=kUuRmp8Jp8fRewHXg@mail.gmail.com>
Subject:	Re: sshd buildup of CLOSE_WAIT leading to unable to function
From:	Joshua Hudson <joshudson AT gmail DOT com>
To:	cygwin <cygwin AT cygwin DOT com>

The interesting detail is it would always stop at exactly 64 sockets
open; which is the maximum number for which select() doesn't have to
spawn a second thread.

Problem disappeared. Given the traces I got the reproduction would
involve somebody's deranged trojan SSH scanner.

64 to too low for Fail2Ban to prevent disaster so I didn't bother. The
fools aren't getting in anyway. I turned off password auth.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -