Re: Broken Sockets

Alan Cox (alan@lxorguk.ukuu.org.uk)
Tue, 21 Dec 1999 17:25:23 +0000 (GMT)


> In my write experiments I have ignored SIGPIPE and grab the error but
> there are two problems. Write doesn't notice a problem until the second
> message is sent and closing the file descriptor still doesn't allow me

That can occur.

> to open a new connection to the server. It says the port is still in
> use even when the server is dropped and comes back up.

The socket has a 2 minute keepalive timer requirement. See the SO_REUSEADDR
option.

> I'm experimenting with the read side now, but was hoping there is
> someplace out there that gets into detail on this subject. There are

Read you may not find about an error for 2 hours.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu