Messages in this thread | | | Date | Wed, 28 Jul 2004 11:09:50 +0200 | From | DervishD <> | Subject | Re: The dreadful CLOSE_WAIT |
| |
Hi William :)
* William Lee Irwin III <wli@holomorphy.com> dixit: > >> Probably best to implement timeouts by hand in your network daemon. > > Of course, this is a bug in the application, but anyway the > > kernel (IMHO) shouldn't allow this. > I suspect the sysctls controlling this, tcp_fin_timeout, tcp_max_orphans, > etc., may be useful to you. Check Documentation/networking/ip-sysctl.txt
tcp_fin_timeout is of no help here, since the server is not stuck in FIN_WAIT2, and in addition to this, the connection is not closed, that is exactly the problem. tcp_max_orphans refer to TCP connections not attached to any user file handle, but a connection in state CLOSE_WAIT is still attached to a file handle, to a valid one indeed.
A grep in the kernel sources didn't give any useful guide about which sysctl parameter will help :((
Thanks anyway, William :) Maybe tcp_max_orphans can help, don't know.
Raúl Núñez de Arenas Coronado
-- Linux Registered User 88736 http://www.pleyades.net & http://raul.pleyades.net/ - 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/
| |