BOUNCE rtl@rtlinux.org: Approval required: (fwd)

[Der Herr Hofrat <der.herr@hofr.at>]

>From owner-rtl Tue Jul 31 01:44:24 2001
Received: from kanga.hofr.at (N735P025.adsl.highway.telekom.at [62.47.35.217])
	by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f6V7iM729214
	for <rtl@fsmlabs.com>; Tue, 31 Jul 2001 01:44:22 -0600
Received: (from hofrat@localhost)
	by kanga.hofr.at (8.10.2/8.10.2/SuSE Linux 8.10.0-0.3) id f6V7jUC15256;
	Tue, 31 Jul 2001 09:45:30 +0200
From: Der Herr Hofrat <der.herr@hofr.at>
Message-Id: <200107310745.f6V7jUC15256@kanga.hofr.at>
Subject: Re: [rtl] Off Topic - Ethernet releasing port addresses
In-Reply-To: <0560141A7916D211A64A00A0C9C9A81505383A75@nwms15.chinalake.navy.mil>
 from "Estabridis, Janet P" at "Jul 30, 2001 07:51:43 am"
To: rtl@fsmlabs.com
Date: Tue, 31 Jul 2001 09:45:30 +0200 (CEST)
CC: "Estabridis, Janet P" <EstabridisJP@navair.navy.mil>
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> I'm using RTLV2.3 and kernel 2.2.14.  I will most likely upgrade
> everything
> to the newer versions, but not until the test system is accepted by the
> customer and that could be 3 months from now.
> 
> I have miniRTL on 8 embedded machines 2 other Linux PC's and 3 Windows
> machines on a local network.  I have both real-time modules running on
> my
> linux PC's and user space applications.  Specifically, the user space
> applications send information to the Windows machines via ethernet
> socket
> code.  I have a set of defined port numbers that the information uses.  
> 
> My problem is that sometimes when I know I have closed the code out and
> I
> restart it I get the message
> 
> Unable to establish a port Connection:  Address already in use. 
> 
> And sometimes I have to re-boot a linux computer to get rid of this
> message

this is happening because one side is not closing the socket cleanly so the 
other side has to listen for the handshake to timeout that is as far as I
know 240s by default - so for this time the address is realy in use . you 
should never need to reboot though - if you check with netstat you will see 
that the port is in "FIN WAIT" state for quite a while if the other end hangs 
up - but latest after timeout*2 ( 8minutes) you should be able to restart 
everything . and at worst if that does not happen do a network stop/start 
- no need to reboot.

hofrat

----- End of forwarded message from owner-rtl@fsmlabs.com -----