Bug#745775: manpages-dev: connect(2) does not document EADDRNOTAVAIL

2014-04-26 Thread Michael Kerrisk (man-pages)
On 04/25/2014 11:02 PM, William Morriss wrote: > Okay I was able to do it without fork. This one been tested on Arch > Linux and Ubuntu. It's simpler I think and also won't give the bind > error. It's below and attached. William, Thanks for that. I've got it now, I think. The point is I think t

Bug#745775: manpages-dev: connect(2) does not document EADDRNOTAVAIL

2014-04-25 Thread William Morriss
Okay I was able to do it without fork. This one been tested on Arch Linux and Ubuntu. It's simpler I think and also won't give the bind error. It's below and attached. William Morriss #include #include #include #include #include #include #include #include #include const int PORTNUM = 24

Bug#745775: manpages-dev: connect(2) does not document EADDRNOTAVAIL

2014-04-25 Thread William Morriss
Due to the complexity of this situation I have to reproduce this is the smallest program I could write that produces "connect: cannot assign requested address". The first run on my machine, it counts to ~220 and then fails with errno 99 on all of the client processes. It then fails immediately if I

Bug#745775: manpages-dev: connect(2) does not document EADDRNOTAVAIL

2014-04-25 Thread Michael Kerrisk (man-pages)
William, this report is a little vague... Do you have a *minimal* program that demonstrates the problem? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#745775: manpages-dev: connect(2) does not document EADDRNOTAVAIL

2014-04-24 Thread William Morriss
Package: manpages-dev Version: 3.40-0 Severity: normal After spawning a bunch (>500) of processes to connect and close connections to the same port on my local machine, connect returned -1 with errno=EADDRNOTAVAIL, which is not described in the manpage connect(2). EADDRNOTAVAIL is defined in /usr