the following effect is also reproduceable with 2.0.29 and 2.0.33 (any
maybe others).
I didn't check 2.1.x kernels.
* Start a X program on a remote Linux machine (e.g. xterm or netscape)
* reset your local machine (reset button, if you don't like to do this,
downing the
machine with network cable removed should work, too :-) The purpose is
to give that machine no chance to gracefully shutdown the TCP
connection.
Now the X app on the remote Linux box hangs around forever. After a week or
so I did a "netstat -t" and the X connection to my local machine was still
in the
established state.
I don't know very much about TCP but I thought, the kernel should notice
over time
that the connection is dead and drop it !? Or is the timeout *that* long?
thanks for any answers,
chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html