Date: Mon, 25 Apr 2005 15:50:22 GMT From: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/80322: TCP socket support broken on a busy port Message-ID: <200504251550.j3PFoM17098501@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/80322; it has been noted by GNATS. From: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl> To: Jan Srzednicki <w@expro.pl> Cc: FreeBSD-gnats-submit@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504251550.j3PFoM17098501>