From owner-freebsd-questions Tue Mar 24 11:11:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15098 for freebsd-questions-outgoing; Tue, 24 Mar 1998 11:11:46 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from garland.bigpanda.com (garland.bigpanda.com [209.125.37.123]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15082 for ; Tue, 24 Mar 1998 11:11:33 -0800 (PST) (envelope-from dvsmith@bigpanda.com) Received: from bigpanda.com (usr45-dialup27.mix2.Boston.mci.net [166.55.78.27]) by garland.bigpanda.com (8.8.7/8.8.5) with ESMTP id MAA15858; Tue, 24 Mar 1998 12:08:42 -0500 (EST) Message-ID: <351804CC.C573B38B@bigpanda.com> Date: Tue, 24 Mar 1998 14:09:01 -0500 From: David Smith X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG CC: dvsmith@bigpanda.com Subject: Sockets stuck in CLOSE_WAIT Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am writing a server on a FreeBSD machine., and am having problems with sockets which are stuck in the CLOSE_WAIT state. I usually notice this error when I kill the server, and try to start it again, it gives an "Address in use" error, because there is a socket on the port,. in the CLOSE_WAIT state. But the program that had that socket open is no longer running. So, why isn't the socket being closed when the process terminates? Any ideas would be appreciated. David Smith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message