From owner-freebsd-hackers Fri Jun 5 12:33:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26790 for freebsd-hackers-outgoing; Fri, 5 Jun 1998 12:33:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26767 for ; Fri, 5 Jun 1998 12:33:01 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA07112; Fri, 5 Jun 1998 13:33:01 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA11091; Fri, 5 Jun 1998 13:32:58 -0600 Date: Fri, 5 Jun 1998 13:32:58 -0600 Message-Id: <199806051932.NAA11091@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Ron G. Minnich" Cc: hackers@FreeBSD.ORG Subject: Re: ECONNREFUSED on a READ? In-Reply-To: References: X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 5606 telnet CALL socket(0x2,0x2,0) > 5606 telnet RET socket 3 > 5606 telnet CALL connect(0x3,0x200ac010,0x10) > 5606 telnet RET connect 0 > 5606 telnet CALL sendto(0x3,0xefbfcfd8,0x16,0,0,0) > 5606 telnet GIO fd 3 wrote 22 bytes > "\^B\M-Z\^A\0\0\^A\0\0\0\0\0\0\^Dc126\0\0\^A\0\^A" > 5606 telnet RET sendto 22/0x16 > 5606 telnet CALL poll(0xefbfcd88,0x1,0x2710) > 5606 telnet RET poll 1 > 5606 telnet CALL recvfrom(0x3,0xefbfd884,0x400,0,0xefbfce10,0xefbfcd7c) > 5606 telnet RET recvfrom -1 errno 61 Connection refused > 5606 telnet CALL close(0x3) > > So we have a socket, make a connection on it, sendto on it, then do a > recvfrom on it and get an error. > > I'm seeing this on a > FreeBSD 3.0-971110-SNAP #0: Sat Jan 6 23:54:11 EST 1996 > root@c064:/usr/src/sys/compile/SMP-CLUSTER > > On almost any program. Do you have a short program that demonstrates this bug? I'd like to see if this is the same sort of problem that the JDK is seeing, since it sounds like it. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message