Error binding socket: address already in use

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. A subsequently started task, that wants to use the same port, gets from bind above error message.This is, in my opinion, wrong behavior, because of the connectionless nature of UDP. Only reboot solves this situation. It looks, as if in net/socket.c, TCP and UDP are handled in the same way without taking into account the different nature of the protocols?!
How can I overcome this problem ?

kind regards

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

Follow-Ups:
- Re: Error binding socket: address already in use
  - From: "linux-os \(Dick Johnson\)" <[email protected]>
- Re: Error binding socket: address already in use
  - From: Alan Cox <[email protected]>
- Re: Error binding socket: address already in use
  - From: "David M. Lloyd" <[email protected]>
- Re: Error binding socket: address already in use
  - From: Jan Engelhardt <[email protected]>

Prev by Date: Re: [PATCH] make ipv4 multicast packets only get delivered to sockets that are joined to group
Next by Date: Re: Linux v2.6.18-rc5
Previous by thread: [PATCH] make ipv4 multicast packets only get delivered to sockets that are joined to group
Next by thread: Re: Error binding socket: address already in use
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]