www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <ma...@znep.com>
Subject Re: os-netbsd/3159: netstat -a -f inet reports many connections in CLOSE_WAIT state
Date Wed, 07 Oct 1998 00:10:01 GMT
The following reply was made to PR os-netbsd/3159; it has been noted by GNATS.

From: Marc Slemko <marcs@znep.com>
To: werther@wservice.com
Cc: apbugs@apache.org
Subject: Re: os-netbsd/3159: netstat -a -f inet reports many connections in
 CLOSE_WAIT state
Date: Tue, 6 Oct 1998 15:55:19 -0700 (PDT)

 On 6 Oct 1998 marc@apache.org wrote:
 
 > [In order for any reply to be added to the PR database, ]
 > [you need to include <apbugs@Apache.Org> in the Cc line ]
 > [and leave the subject line UNCHANGED.  This is not done]
 > [automatically because of the potential for mail loops. ]
 > [If you do not include this Cc, your reply may be ig-   ]
 > [nored unless you are responding to an explicit request ]
 > [from a developer.                                      ]
 > [Reply only with text; DO NOT SEND ATTACHMENTS!         ]
 > 
 > 
 > Synopsis: netstat -a -f inet reports many connections in CLOSE_WAIT state
 > 
 > State-Changed-From-To: open-closed
 > State-Changed-By: marc
 > State-Changed-When: Tue Oct  6 15:52:15 PDT 1998
 > State-Changed-Why:
 > close_wait is a normal part of a connection.  It is normal for
   ^^^^^^^^^^
 
 Sorry, I read TIME_WAIT in your submission.  TIME_WAIT is normal.
 
 > such a state to stay around for several minutes after the
 > connection is closed.  The connection isn't actually open
 > any more and very few resources are used to deal with it, but
 > it is used to keep state to protect against old segments
 > that may still be floating around the network.
 > 
 
 Hang on a sec.  You said they were in CLOSE_WAIT, but you netstat shows
 them in CLOSING.
 
 Can you clarify exactly what you mean and why you think it is a problem?
 

Mime
View raw message