From owner-freebsd-current Wed Feb 26 10:22:35 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04F0737B401; Wed, 26 Feb 2003 10:22:35 -0800 (PST) Received: from mail.flugsvamp.com (ts46-01-qdr3643.mdfrd.or.charter.com [68.118.36.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5A2443F75; Wed, 26 Feb 2003 10:22:33 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by mail.flugsvamp.com (8.12.6/8.12.6) id h1QIMQsj005347; Wed, 26 Feb 2003 12:22:26 -0600 (CST) (envelope-from jlemon) Date: Wed, 26 Feb 2003 12:22:26 -0600 (CST) From: Jonathan Lemon Message-Id: <200302261822.h1QIMQsj005347@mail.flugsvamp.com> To: tjr@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: TCP is still broken X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article you write: >This program, based on one from the Apache 2 configure script, still causes >-current to lock up solid despite the recent bug fixes to the tcptw code. >Explicitly closing connected_s before returning from main() seems to avoid >the problem. Thanks for the test case. I've just committed a fix for this to -current. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message