Messages in this thread | | | Date | Tue, 27 Jul 2004 11:57:51 +0200 | From | DervishD <> | Subject | Re: The dreadful CLOSE_WAIT |
| |
Hi Måns :)
* Måns Rullgård <mru@kth.se> dixit: > > Seems under Linux that, when a connection is in the CLOSE_WAIT > > state, the only wait to go to LAST_ACK is the application doing the > > 'shutdown()' or 'close()'. Doesn't seem to be a timeout for that. > Is that why some programs seem to hang forever when my NAT gateway > decides to drop a connection?
I don't know. Look at the output of your netstat command. If you have connections in the CLOSE_WAIT state related to the NAT gateway, it may be the cause :? But anyway the effect is just the opposite. Is not CLOSE_WAIT state that hangs a program, but a hung program (or at least one not doing its duty) which puts a connection in CLOSE_WAIT state.
Hope this helps.
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/
| |