From owner-freebsd-net Thu Jan 18 7:43:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id BBDDE37B400 for ; Thu, 18 Jan 2001 07:43:17 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA29005; Thu, 18 Jan 2001 10:43:03 -0500 (EST) (envelope-from wollman) Date: Thu, 18 Jan 2001 10:43:03 -0500 (EST) From: Garrett Wollman Message-Id: <200101181543.KAA29005@khavrinen.lcs.mit.edu> To: Ben Smithurst Cc: freebsd-net@FreeBSD.ORG Subject: manual page review: connect(2) EAGAIN error In-Reply-To: <20010118113453.A25127@comp.leeds.ac.uk> References: <20010118113453.A25127@comp.leeds.ac.uk> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Does this look reasonable to people? Based on > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=24125 > +.It Bq Er EAGAIN > +A resource was temporarily unavailable. > +This could indicate there are no port numbers available for use when a port > +number is being chosen automatically. If this is the actual error being returned, then the code is wrong. The correct (as defined in XNSv4.2 and POSIX.1-200x) error is [EADDRNOTAVAIL]. (The definition of bind() reinforces this requirement.) [EAGAIN] is equivalent to the traditional BSD [EWOULDBLOCK], and might be used for connects in non-blocking mode. The new specification requires [EINPROGRESS] as the return value for a non-blocking connect, and [EALREADY] for connect on an already-connected socket. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message