|
From: Guan W. L. <gua...@ap...> - 2003-10-28 00:37:36
|
The problem is they remain in CLOSE_WAIT without clearing up at all. By the way the listener is running in RH Linux 7.2. Rgds, Guan Wee -----Original Message----- From: bee...@li... [mailto:bee...@li...]=20 Sent: Saturday, October 25, 2003 11:05 AM To: bee...@li... Subject: Beepcore-c-users digest, Vol 1 #115 - 1 msg Send Beepcore-c-users mailing list submissions to bee...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/beepcore-c-users or, via email, send a message with subject or body 'help' to bee...@li... You can reach the person managing the list at bee...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Beepcore-c-users digest..." Today's Topics: 1. Re: Listener in CLOSE_WAIT (Darren New) --__--__-- Message: 1 Date: Thu, 23 Oct 2003 11:02:24 -0700 From: Darren New <dn...@sa...> To: Guan Wee LOO <gua...@ap...> CC: bee...@li... Subject: Re: [Beepcore-c-users] Listener in CLOSE_WAIT Guan Wee LOO wrote: > "netstat -an" will show all the TCP/IP states in CLOSE_WAIT. CLOSE_WAIT is a TCP state where the socket is closed, but the kernel is=20 keeping around enough information to properly handle packets that might=20 have been duplicated and then delayed in the network. It prevents a new=20 connection to the socket from accidentally getting confused with a=20 closed connection. CLOSE_WAIT should clear up within 256 seconds of the=20 actual close, all by itself. --=20 Darren New, San Diego CA USA (PST) "He's just a skinhead with a bad haircut." --__--__-- _______________________________________________ Beepcore-c-users mailing list Bee...@li... https://lists.sourceforge.net/lists/listinfo/beepcore-c-users End of Beepcore-c-users Digest |