Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!news.mathworks.com!tank.news.pipex.net!pipex!news.sprintlink.net!futuris!news From: Hugh Brower <hugh@futuris.net> Newsgroups: comp.unix.bsd.freebsd.misc Subject: TCP sockets that don't know when to die Date: 15 Sep 1995 10:06:37 GMT Organization: Futuris Networks Inc. Lines: 13 Message-ID: <43bj7d$40i@kiwi.futuris.net> NNTP-Posting-Host: sdial221.futuris.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 1.1N (Windows; I; 16bit) I've noticed that the web servers tend to leave a lot of TCP sockets hanging in a CLOSING, CLOSE_WAIT or FIN_WAIT state. The httpd server is set to kill idle connections after 60 seconds; however it doesn't kill any of the above mentioned sockets if there is any data waiting in the send queue.. I would be interested to know if there is any way to either force the system to close the socket after a timeout or manually reset all the ones that are in that twilight zone state. TIA, Hugh