Non-Blocking socket (SOCK_STREAM send) - SOLVED

2000-12-15 Thread Adam Scislowicz
I Previously Wrote: > Could someone explain why send is failing with EPIPE on the 2.4.x > kernel, while it is working with the 2.2.x kernels. It turns our the socket family was not being set to AF_INET :/ It was working in 2.2.x because in our situation the sock family was being initialized to A

Re: Non-Blocking socket (SOCK_STREAM send)

2000-12-14 Thread Andi Kleen
On Thu, Dec 14, 2000 at 03:54:16PM -0800, Adam Scislowicz wrote: > > From your subject you seem not to. > > > Im sorry for the subject I just wanted to give the environmental factors, and it is a > non-blocking socket. At this point I am not sure if that is relavent or not. > > > To the best of m

Re: Non-Blocking socket (SOCK_STREAM send)

2000-12-14 Thread Adam Scislowicz
> From your subject you seem not to. > Im sorry for the subject I just wanted to give the environmental factors, and it is a non-blocking socket. At this point I am not sure if that is relavent or not. > To the best of my knowledge the receiver side EPIPE reporting has not changed, > so it must b

Re: Non-Blocking socket (SOCK_STREAM send)

2000-12-14 Thread Andi Kleen
On Thu, Dec 14, 2000 at 03:26:53PM -0800, Adam Scislowicz wrote: > We understand the meaning of EPIPE, the question is why 2.4.x is returning EPIPE, > while 2.2.x is succeeding in sending > the data to thttpd. Using the 2.2.x kernel our proxy functions, and I can access > thttpd directly. In 2.4.x

Re: Non-Blocking socket (SOCK_STREAM send)

2000-12-14 Thread Adam Scislowicz
We understand the meaning of EPIPE, the question is why 2.4.x is returning EPIPE, while 2.2.x is succeeding in sending the data to thttpd. Using the 2.2.x kernel our proxy functions, and I can access thttpd directly. In 2.4.x I can access thttpd directly but the proxy does not function. I have a

Re: Non-Blocking socket (SOCK_STREAM send)

2000-12-14 Thread Andi Kleen
On Thu, Dec 14, 2000 at 03:12:27PM -0800, Adam Scislowicz wrote: > Could someone explain why send is failing with EPIPE on the 2.4.x > kernel, while it is working with the 2.2.x kernels. > > The PsuedoCode: > sock = socket(AF_INET, SOCK_STREAM, 0) > buf = fcntl(sock, F_GETFL) > fcntl(sock, F_SETF

Non-Blocking socket (SOCK_STREAM send)

2000-12-14 Thread Adam Scislowicz
Could someone explain why send is failing with EPIPE on the 2.4.x kernel, while it is working with the 2.2.x kernels. The PsuedoCode: sock = socket(AF_INET, SOCK_STREAM, 0) buf = fcntl(sock, F_GETFL) fcntl(sock, F_SETFL, buf | O_NONBLOCK) // we check the SETFL return value, it succeeds while ((re