From owner-freebsd-bugs@FreeBSD.ORG  Thu Jan 12 14:07:16 2006
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
X-Original-To: freebsd-bugs@hub.freebsd.org
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6444216A41F;
	Thu, 12 Jan 2006 14:07:16 +0000 (GMT)
	(envelope-from glebius@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 164D243D45;
	Thu, 12 Jan 2006 14:07:16 +0000 (GMT)
	(envelope-from glebius@FreeBSD.org)
Received: from freefall.freebsd.org (glebius@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k0CE7FQL004199;
	Thu, 12 Jan 2006 14:07:15 GMT
	(envelope-from glebius@freefall.freebsd.org)
Received: (from glebius@localhost)
	by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k0CE7D3Z004195;
	Thu, 12 Jan 2006 14:07:13 GMT (envelope-from glebius)
Date: Thu, 12 Jan 2006 14:07:13 GMT
From: Gleb Smirnoff <glebius@FreeBSD.org>
Message-Id: <200601121407.k0CE7D3Z004195@freefall.freebsd.org>
To: bachue@bachue.com, glebius@FreeBSD.org, freebsd-bugs@FreeBSD.org
Cc: 
Subject: Re: kern/31746: failed connect(2) seems to cause problems with
	socket
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2006 14:07:16 -0000

Synopsis: failed connect(2) seems to cause problems with socket

State-Changed-From-To: open->closed
State-Changed-By: glebius
State-Changed-When: Thu Jan 12 14:05:59 UTC 2006
State-Changed-Why: 
This is a POSIX compliant behavior. Quoting

http://www.opengroup.org/onlinepubs/000095399/functions/connect.html

"If connect() fails, the state of the socket is unspecified. Conforming
applications should close the file descriptor and create a new socket
before attempting to reconnect."

http://www.freebsd.org/cgi/query-pr.cgi?pr=31746