From owner-freebsd-current Fri Oct 16 10:38:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00577 for freebsd-current-outgoing; Fri, 16 Oct 1998 10:38:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00558 for ; Fri, 16 Oct 1998 10:38:39 -0700 (PDT) (envelope-from root@psa.at) Received: from uvo-108.univie.ac.at ([131.130.230.108] helo=entropy.quake.at) by darkstar.psa.at with esmtp (Exim 2.05 #1) id 0zUDom-0003yx-00 for current@freebsd.org; Fri, 16 Oct 1998 19:37:38 +0200 Received: from localhost ([127.0.0.1]) by entropy.quake.at with esmtp (Exim 2.05 #1) id 0zUBps-0000Wu-00 for current@freebsd.org; Fri, 16 Oct 1998 17:30:36 +0200 Date: Fri, 16 Oct 1998 17:30:36 +0200 (CEST) From: Alexander Sanda X-Sender: root@darkstar.vmx To: current@FreeBSD.ORG Subject: How to get rid of a CLOSE_WAIT connection ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, here is the story: On one of my boxes, running 3.0-BETA, I mistakenly killed xinetd while I was remotely logged in via ssh. Bad thing(tm), but I could manage to get some guy of the office staff to log in and restart xinetd. Now, I note, that netstat -na still shows a connection from this machine:port22 to my former ip adress:some_port (the ip adress, I have been assigned, when the accident happened). The connection is reported to be in CLOSE_WAIT state. Obviously, xinetd cannot bind to port 22, because this port is still used, and waiting for something to happen :) In fact, the Revc-Q field also shows a non-zero value. Will this ever go away (it's now about 17 hrs since this happened) ? BTW: some other thing: Now after 3.0-RELEASE has seen the world, what's the correct cvsup tag to stay with 3.0 ? Is it RELENG_3_0 ? -- # /AS/ http://privat.schlund.de/entropy/ # # GNU is not Unix, BSD is. # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message