From owner-freebsd-questions Tue Mar 24 11:46:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20616 for freebsd-questions-outgoing; Tue, 24 Mar 1998 11:46:21 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from general1.consumersedge.com (mail.personalogic.com [208.213.67.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20596 for ; Tue, 24 Mar 1998 11:46:15 -0800 (PST) (envelope-from dshanes@personalogic.com) Received: from SHANES by general1.consumersedge.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1458.49) id HQLPJXTM; Tue, 24 Mar 1998 11:46:27 -0800 Message-ID: <016801bd575d$2373f960$1d43a8c0@shanes.personalogic.com> From: "David Shanes" To: "David Smith" , Cc: Subject: Re: Sockets stuck in CLOSE_WAIT Date: Tue, 24 Mar 1998 11:43:37 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you aborting the Server? You should use the shutdown(int skt, int flag) command to ensure it gracefully shuts down the server. David _____________________________________________________ David Shanes 7535 Metropolitan Drive dshanes@personalogic.com San Diego, CA 92108 Database Developer (619) 220-5800 x228 PersonaLogic, Inc. (619) 220-5899 (fax) http://www.PersonaLogic.com -----Original Message----- From: David Smith To: freebsd-questions@FreeBSD.ORG Cc: dvsmith@bigpanda.com Date: Tuesday, March 24, 1998 11:28 AM Subject: Sockets stuck in CLOSE_WAIT >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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message