Closing a port

Jason Rogers jacaetevha at
Tue May 10 13:52:35 UTC 2005

On Mon, 09 May 2005 11:10:23 -0700, Mike O'Brien <obrien at>  

> 	"netstat" tells the truth but the truth, as always, may
> be more complex than you were expecting.  A closed TCP port can
> hang around for quite a while in state FIN_WAIT_2, depending on
> the vagaries of the TCP implementation at the far end.  The
> port's still closed, it's just that kernel resources haven't
> been freed up yet.  They will be.  Meanwhile, it still shows
> up in "netstat".
> Mike O'Brien

That's precisely what I meant about misinterpreted results.  Thank you for  
flushing it out so I know exactly why...  I love this community. ;)

Jason Rogers

"I am crucified with Christ: nevertheless I live; yet not I,
but Christ liveth in me: and the life which I now live in
the flesh I live by the faith of the Son of God, who loved
me, and gave himself for me."
     Galatians 2:20

More information about the Squeak-dev mailing list