Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Oct 1998 17:30:36 +0200 (CEST)
From:      Alexander Sanda <as@psa.at>
To:        current@FreeBSD.ORG
Subject:   How to get rid of a CLOSE_WAIT connection ?
Message-ID:  <Pine.BSF.4.05.9810161653480.335-100000@darkstar.vmx>

next in thread | raw e-mail | index | archive | help

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9810161653480.335-100000>