From owner-freebsd-questions Mon Feb 1 15:43:16 1999
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA06657
for freebsd-questions-outgoing; Mon, 1 Feb 1999 15:43:16 -0800 (PST)
(envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06645
for <freebsd-questions@freebsd.org>; Mon, 1 Feb 1999 15:42:58 -0800 (PST)
(envelope-from ben@scientia.demon.co.uk)
Received: from ben by scientia.demon.co.uk with local (Exim 2.11 #1)
id 107RPg-000IIl-00
for freebsd-questions@freebsd.org; Mon, 1 Feb 1999 22:01:48 +0000
Date: Mon, 1 Feb 1999 22:01:48 +0000
From: Ben Smithurst <ben@scientia.demon.co.uk>
To: freebsd-questions@FreeBSD.ORG
Subject: tcp connections in CLOSING state
Message-ID: <19990201220148.A70332@scientia.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
There seems to be a tcp connection stuck in the CLOSING state here, which
seems odd. It doesn't seem to be causing any problems, but I imagine if
they start accumulating it could cause a problem. So, my questions are,
1. What could have caused a connection to get stuck like that?
2. How should I get rid of it? (if possible, without rebooting.)
Also, connections do seem to stick in this state fairly often, but timeout
after a while (this problematic one has been there for hours). Is there
any way to change the timeout on the CLOSING state? It's probably
somewhere in the source, but I don't know much about C, less about kernel
internals, and couldn't spot anything obvious looking under /sys/netinet.
Cheers
--
Ben Smithurst
ben@scientia.demon.co.uk
send a blank message to ben+pgp@scientia.demon.co.uk for PGP key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message