Return-Path: william@bourbon.usc.edu
Delivery-Date: Sun Sep  7 14:44:13 2008
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham
	version=3.2.3
Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75])
	by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m87LiDdg012030
	for <cs551@merlot.usc.edu>; Sun, 7 Sep 2008 14:44:13 -0700
Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1])
	by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m87Lh2BF019257
	for <cs551@merlot>; Sun, 7 Sep 2008 14:43:02 -0700
Message-Id: <200809072143.m87Lh2BF019257@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: 551: TIME_WAIT
Date: Sun, 07 Sep 2008 14:43:02 -0700
From: Bill Cheng <william@bourbon.usc.edu>

Someone wrote:

  > after both client and server have closed their sockets and shutdown 
  > 'gracefully' a " netstat -a | grep $port " command still shows them in a 
  > 'TIME_WAIT' state for about 30 seconds. do we need to handle this, if yes 
  > how. thanks

Please look for SO_REUSEADDR in the spec!
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>