Messages in this thread | | | Date | Fri, 05 Apr 2002 03:02:51 -0800 (PST) | Subject | Re: socket write(2) after remote shutdown(2) problem ? | From | "David S. Miller" <> |
| |
From: Stelian Pop <stelian.pop@fr.alcove.com> Date: Fri, 5 Apr 2002 12:55:09 +0200
> * client socket receives a TCP reset How is the client socket supposed to know it received a TCP reset (I am talking from the application point of view, not the kernel...) ?
You may find out by attempting to read data, or you may use the extended IP error reporting Linux has.
But all of this is irrelevant. When a server closes and says "send me no more data", this implies that the server told the client it doesn't want any more data. If the client sends data, this is a gross fatal error, so TCP resets in FIN_WAIT{1,2} states.
RFC 793 originally specified to queue the data, RFC 1122 is where the current behavior is defined.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |