Date: Thu, 12 Jan 2006 14:07:13 GMT From: Gleb Smirnoff <glebius@FreeBSD.org> To: bachue@bachue.com, glebius@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/31746: failed connect(2) seems to cause problems with socket Message-ID: <200601121407.k0CE7D3Z004195@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601121407.k0CE7D3Z004195>