From owner-freebsd-stable Sat Jan 16 21:19:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04794 for freebsd-stable-outgoing; Sat, 16 Jan 1999 21:19:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from implode.root.com (root.com [208.221.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04789 for ; Sat, 16 Jan 1999 21:19:36 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id VAA05557; Sat, 16 Jan 1999 21:16:32 -0800 (PST) Message-Id: <199901170516.VAA05557@implode.root.com> To: Jason Evans cc: freebsd-stable@FreeBSD.ORG Subject: Re: connect() returns EAGAIN In-reply-to: Your message of "Sat, 16 Jan 1999 21:05:13 PST." From: David Greenman Reply-To: dg@root.com Date: Sat, 16 Jan 1999 21:16:32 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I've been working on some code that does a non-blocking socket connect(). >According to the manpage and Stevens's UNP 2nd Ed., connect() should >return EINPROGRESS if the connection isn't able to be established >immediately. -stable returns EAGAIN instead. EAGAIN appears to be an >invalid return value for connect(). This problem doesn't appear to exist >under -current. > >Is this the sort of thing that is likely to get fixed in the 2.2.x branch >at this point, or is this too insignificant to fix now? The 2.2.x branch is escentially dead. I suppose someone might commit a security fix of some sort, but no further releases will be made from it. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message