Date: Thu, 18 Jan 2001 10:43:03 -0500 (EST) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Ben Smithurst <csxbcs@comp.leeds.ac.uk> Cc: freebsd-net@FreeBSD.ORG Subject: manual page review: connect(2) EAGAIN error Message-ID: <200101181543.KAA29005@khavrinen.lcs.mit.edu> In-Reply-To: <20010118113453.A25127@comp.leeds.ac.uk> References: <20010118113453.A25127@comp.leeds.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Thu, 18 Jan 2001 11:34:54 +0000, Ben Smithurst <csxbcs@comp.leeds.ac.uk> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101181543.KAA29005>