From owner-freebsd-questions@FreeBSD.ORG Thu Apr 21 19:46:28 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7A9516A4CE for ; Thu, 21 Apr 2005 19:46:28 +0000 (GMT) Received: from orb.pobox.com (orb.pobox.com [207.8.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C3A843D45 for ; Thu, 21 Apr 2005 19:46:28 +0000 (GMT) (envelope-from LukeD@pobox.com) Received: from orb (localhost [127.0.0.1]) by orb.pobox.com (Postfix) with ESMTP id 296347D8 for ; Thu, 21 Apr 2005 15:46:25 -0400 (EDT) Received: from pool-71-112-215-205.sttlwa.dsl-w.verizon.net (pool-71-112-215-205.sttlwa.dsl-w.verizon.net [71.112.215.205]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by orb.sasl.smtp.pobox.com (Postfix) with ESMTP id 9426887 for ; Thu, 21 Apr 2005 15:46:24 -0400 (EDT) Date: Thu, 21 Apr 2005 12:46:18 -0700 (PDT) From: LukeD@pobox.com X-X-Sender: lukas@border.crystalsphere.multiverse To: freebsd-questions@freebsd.org Message-ID: <20050421123644.U6491@border.crystalsphere.multiverse> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Reusing a port after a crash X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: LukeD@pobox.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 19:46:28 -0000 >From time to time, my torrent filesharing application will crash or need to be killed. The application is configured to listen on a specific port. If I try to restart the application after improper termination, I receive a fatal error message stating that the port is already in use. Before restarting the application, I verify that the application did indeed shut down (via 'ps -aux') and 'sockstat -l' shows that no application is using the port in question, so I don't understand how the port could still be 'in use'. The only way I've found to restart the application after improper termination is to reboot the whole system. Is there something else I could try? Does this kind of thing tend to happen to network applications when they crash or could this be specific to my application? Luke Dean