linux-kernel - Re: Error binding socket: address already in use

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1158161015.13977.27.camel@localhost.localdomain>
Date:	Wed, 13 Sep 2006 16:23:35 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Peter Lezoch <pledr@...nline.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Error binding socket: address already in use

Ar Mer, 2006-09-13 am 14:41 +0000, ysgrifennodd Peter Lezoch:
> Hi,
> killing a server task that is operating on a UDP socket( AF_INET,
> SOCK_DGRAM, IPPROTO_UDP ), leaves the socket in an unclosed state. 

For UDP the socket closes at the point the last user of the socket
closes. For TCP there is a time delay mandated by the specification.

If you are seeing UDP sockets remain open when you kill a server make
sure it hasn't forked other processes and passed them the file handle.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/