From owner-freebsd-net  Fri Jan 19  9:36:56 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 69AA037B400
	for <freebsd-net@FreeBSD.ORG>; Fri, 19 Jan 2001 09:36:38 -0800 (PST)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA10929;
	Fri, 19 Jan 2001 12:36:27 -0500 (EST)
	(envelope-from wollman)
Date: Fri, 19 Jan 2001 12:36:27 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200101191736.MAA10929@khavrinen.lcs.mit.edu>
To: Wes Peters <wes@softweyr.com>
Cc: freebsd-net@FreeBSD.ORG
Subject: Re: manual page review: connect(2) EAGAIN error
In-Reply-To: <3A686C0E.D48EC7E9@softweyr.com>
References: <20010118113453.A25127@comp.leeds.ac.uk>
	<200101181543.KAA29005@khavrinen.lcs.mit.edu>
	<20010119101915.B16961@comp.leeds.ac.uk>
	<200101191557.KAA10198@khavrinen.lcs.mit.edu>
	<3A686C0E.D48EC7E9@softweyr.com>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

<<On Fri, 19 Jan 2001 09:32:14 -0700, Wes Peters <wes@softweyr.com> said:

> If the code implements what?  Returning EAGAIN when no ephemeral ports are
> available?  That is all the above really says, and then provides a hint
> as to how to fix it.  The description is a little simplistic, as it misses
> the lowfirst-lowlast and highfirst-highlast ranges.

If no ports are available, the correct (Standard) error is
[EADDRNOTAVAIL], regardless of whether the socket is in blocking or
non-blocking mode.

-GAWollman



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message