kern/80322: TCP socket support broken on a busy port
Pawel Malachowski
pawmal-posting at freebsd.lublin.pl
Mon Apr 25 08:50:23 PDT 2005
The following reply was made to PR kern/80322; it has been noted by GNATS.
From: Pawel Malachowski <pawmal-posting at freebsd.lublin.pl>
To: Jan Srzednicki <w at expro.pl>
Cc: FreeBSD-gnats-submit at freebsd.org
Subject: Re: kern/80322: TCP socket support broken on a busy port
Date: Mon, 25 Apr 2005 17:42:57 +0200
On Mon, Apr 25, 2005 at 02:16:50PM +0200, Jan Srzednicki wrote:
> After a server daemon listening on a very busy unprivileged (>1024) port
> dies (I'm not able to repeat that with a low-usage port), the port is
> closed as it should, sockstat doesn't show anything listening on it,
> everything looks fine. But an attempt to bind to that port with UID != 0
> results in failure -- EADDRINUSE.
Hm, I saw behaviour like this on 4.8 machine running some shoutcast
server; after killing radio process it was unable to bind to port
as if it was already open (nothing was listening on it) but after
a minute or so it was able to bind again. I've never investigated
this.
--
Pawe³ Ma³achowski
More information about the freebsd-bugs
mailing list