<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3243" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=363461015-29012008><FONT face=Arial
color=#0000ff size=2>What OS? Some operating systems allow network
connections to hang around a bit after disconnection. On Solaris you can
set a parameter to reduce the timeout period. Hobbit could trigger this
because each client connects to the server, sends a data blast, and then
disconnects.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Gary Baluha [mailto:gumby3203@gmail.com]
<BR><B>Sent:</B> Tuesday, January 29, 2008 8:58 AM<BR><B>To:</B>
hobbit@hswn.dk<BR><B>Subject:</B> [hobbit] Large number of
TIME_WAITs<BR></FONT><BR></DIV>
<DIV></DIV>I noticed something strange on my Hobbit server, though I'm not
sure if it's a problem or not. There are about 140 TIME_WAITs from the
local IP of the Hobbit server, and about 30 TIME_WAITs from localhost, all
using port 1984. They look something like
this:<BR><BR>0 0 <A
href="http://1.2.3.4:42389">1.2.3.4:42389</A>
<A
href="http://1.2.3.4:1984">1.2.3.4:1984</A>
TIME_WAIT<BR>0 0 <A
href="http://1.2.3.4:42394">1.2.3.4:42394</A>
<A
href="http://1.2.3.4:1984">1.2.3.4:1984</A>
TIME_WAIT<BR>0 0 <A
href="http://1.2.3.4:42399">1.2.3.4:42399</A>
<A
href="http://1.2.3.4:1984">1.2.3.4:1984</A>
TIME_WAIT<BR>0 0 <A
href="http://1.2.3.4:42396">1.2.3.4:42396</A>
<A
href="http://1.2.3.4:1984">1.2.3.4:1984</A>
TIME_WAIT<BR>0 0 <A
href="http://1.2.3.4:42397">1.2.3.4:42397</A>
<A
href="http://1.2.3.4:1984">1.2.3.4:1984</A>
TIME_WAIT<BR><BR>0 0 <A
href="http://127.0.0.1:42310">127.0.0.1:42310</A>
<A
href="http://127.0.0.1:1984">127.0.0.1:1984</A>
TIME_WAIT<BR>0 0 <A
href="http://127.0.0.1:42309">127.0.0.1:42309</A>
<A
href="http://127.0.0.1:1984">127.0.0.1:1984</A>
TIME_WAIT<BR>0 0 <A
href="http://127.0.0.1:42315">127.0.0.1:42315</A>
<A
href="http://127.0.0.1:1984">127.0.0.1:1984</A>
TIME_WAIT<BR>0 0 <A
href="http://127.0.0.1:42322">127.0.0.1:42322</A>
<A
href="http://127.0.0.1:1984">127.0.0.1:1984</A>
TIME_WAIT<BR>0 0 <A
href="http://127.0.0.1:42320">127.0.0.1:42320</A>
<A
href="http://127.0.0.1:1984">127.0.0.1:1984</A>
TIME_WAIT<BR><BR>There are also a few on various other
ports:<BR>0 0 <A
href="http://127.0.0.1:42246">127.0.0.1:42246</A>
<A
href="http://127.0.0.1:29021">127.0.0.1:29021</A>
TIME_WAIT<BR>0 0 <A
href="http://127.0.0.1:42301">127.0.0.1:42301</A>
<A
href="http://127.0.0.1:29023">127.0.0.1:29023</A>
TIME_WAIT<BR>0 0 <A
href="http://127.0.0.1:42362">127.0.0.1:42362</A>
<A
href="http://127.0.0.1:29017">127.0.0.1:29017</A>
TIME_WAIT<BR>0 0 <A
href="http://127.0.0.1:29030">127.0.0.1:29030</A>
<A
href="http://127.0.0.1:42380">127.0.0.1:42380</A>
TIME_WAIT<BR>0 0 <A
href="http://127.0.0.1:42348">127.0.0.1:42348</A>
<A
href="http://127.0.0.1:29019">127.0.0.1:29019</A>
TIME_WAIT<BR><BR><BR>Any idea why there should be so many of them,
particularly on the localhost address? And any idea if this looks
abnormal or not?<BR></BLOCKQUOTE></BODY></HTML>