Return to BSD News archive
#! rnews 1298 bsd Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!newsfeed.internetmci.com!ionews.ionet.net!usenet From: "Chuck McCollum" <chuck@siege.net> Newsgroups: comp.unix.bsd.bsdi.misc Subject: Why dont some network sockets die, and how do i kill them? Date: 25 Apr 1997 10:18:33 GMT Organization: Connect America Lines: 23 Message-ID: <01bc5161$d8cfb5e0$105881d0@siege.net.siege.net> NNTP-Posting-Host: pxsip06.ionet.net X-Newsreader: Microsoft Internet News 4.70.1155 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:6752 Sometimes there are some TCP sockets that stay open (usually connected to remote hosts port 80), and by doing a netstat, their status is shown as "FIN_WAIT2", or some variation. These buggers stay that way for days. Now the problem. If opening a socket (which ultimately hangs due to a lack of responce by the remote server) by a program, the program itself must die, and restart in order to move on. Timeouts do not seem to work. Issueing control characters dont work. Nothing seems to work to kill them. They just wont die.... ahhhhh!. What can be done to Kill these persistant network sockets. Any help appreciated! Please respond to: chuck@siege.net CC to: wsite@siege.net