lkml.org 
[lkml]   [1999]   [May]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Likely cause of EAGAIN in connect() in 2.2.8??
On Thu, May 13, 1999 at 04:39:46PM +0200, Matthew Wilcox wrote:
> On Thu, May 13, 1999 at 01:13:18AM -0700, David S. Miller wrote:
> > Date: Wed, 12 May 1999 21:21:06 +0800
> > From: David Luyer <luyer@ucs.uwa.edu.au>
> >
> > The EAGAIN error code is not a documented return code from
> > connect() in the manual pages on my Debian Linux 2.1 system.
> >
> > It is a documentation bug then, as this has been the valid return
> > value from stream connects under Linux for quite a long time.
>
> Noted. netman edition of connect(2) updated to reflect this:
>
> EAGAIN No ports are available. The task should retry
> later.
>
> netman is coming on quite well, I suspect there will be a release
> within a couple of weeks.

I already fixed it in CVS.

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:51    [W:0.951 / U:0.252 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site