From owner-freebsd-hackers Tue Jul 25 12:39:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f194.law7.hotmail.com [216.33.237.194]) by hub.freebsd.org (Postfix) with SMTP id AE4C537B927 for ; Tue, 25 Jul 2000 12:39:17 -0700 (PDT) (envelope-from johnnyteardrop@hotmail.com) Received: (qmail 37722 invoked by uid 0); 25 Jul 2000 19:39:16 -0000 Message-ID: <20000725193916.37721.qmail@hotmail.com> Received: from 209.249.186.215 by www.hotmail.com with HTTP; Tue, 25 Jul 2000 12:39:16 PDT X-Originating-IP: [209.249.186.215] From: "Greg Thompson" To: freebsd-hackers@freebsd.org Subject: odd accept(2) behavior Date: Tue, 25 Jul 2000 15:39:16 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hackers, i'm seeing some fairly odd behavior from accept(2) when the connecting socket goes away at just the right time. the timing is fairly funky, so i don't know if i can easily whip up a repro for this, but what i'm seeing is: accept returns a positive value (ie: not an error), but sets the addrlen to zero. a subsequent call to getsockname with the new socket returns -1 and sets errno to ECONNRESET. is this the expected behavior? can someone explain? i haven't observed this on any other platforms i've been hacking lately. thanks. -- -greg ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message