Re: A call to revise sockets behaviour

2013-07-29 Thread John Heffner
On Mon, Jul 29, 2013 at 2:02 PM, Artem S. Tashkinov wrote: > Jul 29, 2013 11:43:00 PM, Eric wrote: > On Mon, 2013-07-29 at 15:47 +, Artem S. Tashkinov wrote: >> >>> A wine developer clearly showed that this option simply doesn't work. >>> >>> http://bugs.winehq.org/show_bug.cgi?id=26031#c21 >>

Re: A call to revise sockets behaviour

2013-07-29 Thread Artem S. Tashkinov
Jul 29, 2013 11:43:00 PM, Eric wrote: On Mon, 2013-07-29 at 15:47 +, Artem S. Tashkinov wrote: > >> A wine developer clearly showed that this option simply doesn't work. >> >> http://bugs.winehq.org/show_bug.cgi?id=26031#c21 >> >> Output of strace: >> getsockopt(24, SOL_SOCKET, SO_REUSEADDR,

Re: A call to revise sockets behaviour

2013-07-29 Thread Eric Dumazet
On Mon, 2013-07-29 at 15:47 +, Artem S. Tashkinov wrote: > A wine developer clearly showed that this option simply doesn't work. > > http://bugs.winehq.org/show_bug.cgi?id=26031#c21 > > Output of strace: > getsockopt(24, SOL_SOCKET, SO_REUSEADDR, [0], [4]) = 0 > setsockopt(24, SOL_SOCKET, S

Re: A call to revise sockets behaviour

2013-07-29 Thread Artem S. Tashkinov
Jul 29, 2013 11:27:00 PM, rick wrote: >> A wine developer clearly showed that this option simply doesn't work. >> >> http://bugs.winehq.org/show_bug.cgi?id=26031#c21 >> >> Output of strace: >> getsockopt(24, SOL_SOCKET, SO_REUSEADDR, [0], [4]) = 0 >> setsockopt(24, SOL_SOCKET, SO_REUSEADDR, [1], 4

Re: A call to revise sockets behaviour

2013-07-29 Thread Rick Jones
A wine developer clearly showed that this option simply doesn't work. http://bugs.winehq.org/show_bug.cgi?id=26031#c21 Output of strace: getsockopt(24, SOL_SOCKET, SO_REUSEADDR, [0], [4]) = 0 setsockopt(24, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 bind(24, {sa_family=AF_INET, sin_port=htons(43012

Re: A call to revise sockets behaviour

2013-07-29 Thread Artem S. Tashkinov
Jul 29, 2013 09:35:25 PM, Stephen wrote: On Mon, 29 Jul 2013 15:10:34 + (UTC) >"Artem S. Tashkinov" wrote: > >> Hello, >> >> Currently the Linux kernel disallows to start listening on a TCP/UDP socket >> if >> there are open connections against the port, regardless connections status. >> So

Re: A call to revise sockets behaviour

2013-07-29 Thread Stephen Hemminger
On Mon, 29 Jul 2013 15:10:34 + (UTC) "Artem S. Tashkinov" wrote: > Hello, > > Currently the Linux kernel disallows to start listening on a TCP/UDP socket if > there are open connections against the port, regardless connections status. > So even > if _all_ you have is some stale (i.e. no lon

A call to revise sockets behaviour

2013-07-29 Thread Artem S. Tashkinov
Hello, Currently the Linux kernel disallows to start listening on a TCP/UDP socket if there are open connections against the port, regardless connections status. So even if _all_ you have is some stale (i.e. no longer active connections pending destruction) the kernel will not allow to reuse thi