From owner-freebsd-net Mon Feb 12 9:56:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id F3D8237B503 for ; Mon, 12 Feb 2001 09:56:27 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id JAA90169; Mon, 12 Feb 2001 09:56:26 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id JAA71541; Mon, 12 Feb 2001 09:56:26 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200102121756.JAA71541@curve.dellroad.org> Subject: Re: [itojun@iijlab.net: accept(2) behavior with tcp RST right after handshake] In-Reply-To: <20010211165612.A3148@mollari.cthul.hu> "from Kris Kennaway at Feb 11, 2001 04:56:12 pm" To: Kris Kennaway Date: Mon, 12 Feb 2001 09:56:26 -0800 (PST) Cc: Jonathan Lemon , net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kennaway writes: > Did you guys agree on a commit-worthy fix yet? I wasn't party to the issue that generated this thread in the first place, but.. I think the concensus is that if accept(2) returns an error then this will break some applications, so instead it should return a socket which will itself return an error on the first operation. Somebody correct me if I'm wrong. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message