Re: socket leak in 2.2.12 and 2.2.14..?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello!

> Moreover the port leak is confirmed by the high tcp_bind_bucket value. The
> question is how can a program(assuming its a bug in the code)  possibly occupy
> more ports than it does connections (including TIME_WAIT ones).

It allocates exactly that number of ports, which it used.


Each timewait socket lives minimum for 60 seconds, so that
with default setup brainless program cannot make more
than 4000/60=66 connections per second. Even if you tune
sysctl values to more sane one, it will be able to make
only about 500 connections per second.

If you need more, teach it to use SO_REUSEADDR properly.

Alexey
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux