Re: manual page review: connect(2) EAGAIN error

2001-01-20 Thread Wes Peters
Dima Dorfman wrote: > > > oops, looks like you already answered that (EADDRNOTAVAIL) in your last > > message. sorry. If you fix the code to return EADDRNOTAVAIL then the PR > > can be closed as it will no longer apply. > > I sent a patch to fix this in a response to this thread, but it seems >

Re: manual page review: connect(2) EAGAIN error

2001-01-20 Thread Dima Dorfman
> oops, looks like you already answered that (EADDRNOTAVAIL) in your last > message. sorry. If you fix the code to return EADDRNOTAVAIL then the PR > can be closed as it will no longer apply. I sent a patch to fix this in a response to this thread, but it seems noone noticed. You can find the e

Re: manual page review: connect(2) EAGAIN error

2001-01-20 Thread Ben Smithurst
Garrett Wollman wrote: > < said: > >> +.It Bq Er EAGAIN >> +A resource was temporarily unavailable when connecting a socket in >> +non-blocking mode. >> +This could indicate there are no port numbers available for use when a port >> +number is being chosen automatically. >> +Increasing the >> +.

Re: manual page review: connect(2) EAGAIN error

2001-01-20 Thread Ben Smithurst
> if (count-- < 0) { /* completely used? */ > /* >* Undo any address bind that may have >* occurred above. >*/ > in

Re: manual page review: connect(2) EAGAIN error

2001-01-19 Thread Dima Dorfman
> < 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 ran

Re: manual page review: connect(2) EAGAIN error

2001-01-19 Thread Garrett Wollman
< 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

Re: manual page review: connect(2) EAGAIN error

2001-01-19 Thread Wes Peters
Garrett Wollman wrote: > > < said: > > > +.It Bq Er EAGAIN > > +A resource was temporarily unavailable when connecting a socket in > > +non-blocking mode. > > +This could indicate there are no port numbers available for use when a port > > +number is being chosen automatically. > > +Increasing t

Re: manual page review: connect(2) EAGAIN error

2001-01-19 Thread Garrett Wollman
< said: > +.It Bq Er EAGAIN > +A resource was temporarily unavailable when connecting a socket in > +non-blocking mode. > +This could indicate there are no port numbers available for use when a port > +number is being chosen automatically. > +Increasing the > +.Va net.inet.ip.portrange.last > +.X

Re: manual page review: connect(2) EAGAIN error

2001-01-19 Thread Ben Smithurst
Garrett Wollman wrote: > [EAGAIN] is equivalent to the traditional BSD [EWOULDBLOCK], and might > be used for connects in non-blocking mode. oops, I forgot that this is for non-blocking sockets... +.It Bq Er EAGAIN +A resource was temporarily unavailable when connecting a socket in +non-blockin

Re: manual page review: connect(2) EAGAIN error

2001-01-18 Thread Garrett Wollman
< said: > the ``.Brq Va sysctl.variable'' should be used. Why introduce .Sc? For the same reason as we have .Er in addition to .Dv. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message

Re: manual page review: connect(2) EAGAIN error

2001-01-18 Thread Ruslan Ermilov
On Thu, Jan 18, 2001 at 10:47:00AM -0500, Garrett Wollman wrote: > < said: > > >> +Increasing the > >> +.Va net.inet.ip.portrange.last > > +sysctl variable > >> +(which defaults to 5000) may help this problem. > > We really should define a special markup for these so that it is not > necessary

Re: manual page review: connect(2) EAGAIN error

2001-01-18 Thread Garrett Wollman
< said: >> +Increasing the >> +.Va net.inet.ip.portrange.last > +sysctl variable >> +(which defaults to 5000) may help this problem. We really should define a special markup for these so that it is not necessary to so frequently repeat this. POSIX uses {braces} for potentially-configurable sy

manual page review: connect(2) EAGAIN error

2001-01-18 Thread Garrett Wollman
< 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 t

Re: manual page review: connect(2) EAGAIN error

2001-01-18 Thread Ben Smithurst
Ben Smithurst wrote: > +This could indicate there are no port numbers available for use when a port > +number is being chosen automatically. > +Increasing the > +.Va net.inet.ip.portrange.last +sysctl variable > +(which defaults to 5000) may help this problem. oops. -- Ben Smithurst / [EMAIL

manual page review: connect(2) EAGAIN error

2001-01-18 Thread Ben Smithurst
Does this look reasonable to people? Based on http://www.FreeBSD.org/cgi/query-pr.cgi?pr=24125 --- connect.2 2000/11/22 16:01:11 1.14 +++ connect.2 2001/01/18 11:28:14 @@ -142,6 +142,13 @@ The socket is non-blocking and a previous connection attempt has not yet been completed. +.It Bq