search for: ____but___

...rprised as well, I was getting very frequent EPIPE errors when testing connection from my home to my server in the university. My "testing environment" has changed radically, at that time I had an ISDN connection, now I've lost it (got DSL), neverthelles I will try to recreate it. ____But___, there was a serious bug which could be the "real" one and was masked by the "poll()" for a while. I've described it in a previous mail and sent the one-liner patch: ------ The problem resided on the conditional variable being signaled twice (or more) after new connectio...

On 24/02/02 05:02, Jack Moffitt shaped the electrons to say: > > - The server didn't check for the status of the client's socket before > > the unblocking send(). This caused a disconnection at a minimun network > > congestion, causing a broken pipe error (Linux 2.4 behaviour?) in the > > network. I've just added a poll in sock.c.> > Can you send me this