On Thu, Jan 15, 2015 at 03:40:08PM -0300, Glenn Eychaner wrote: > My only theory is that this has something to do with non-ephemeral ports and > socket reuse, but I'm not sure what. If you want a quick detection that the link is dead, have the server occasionally send bytes to the dos box. You will get an immediate error if the dos box is up and knows that connection is kaput. Given that the port numbers of the new connection are the same, I'm kind of surprised that the behavior changed from 6.5 to 6.6, but, I always use defensive programming (sending those extra bytes). -- greg _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: Socket behavior change from 6.5 to 6.6
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: Socket behavior change from 6.5 to 6.6
- From: Greg Lindahl <lindahl@xxxxxxx>
- Date: Thu, 15 Jan 2015 11:10:46 -0800
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <2A32A6AC-941B-4E16-AB4B-11C45A637729@mac.com>
- User-agent: Mutt/1.4.2.2i
- Follow-Ups:
- Re: Socket behavior change from 6.5 to 6.6
- From: Alexander Farber
- Re: Socket behavior change from 6.5 to 6.6
- References:
- Socket behavior change from 6.5 to 6.6
- From: Glenn Eychaner
- Socket behavior change from 6.5 to 6.6
- Prev by Date: What happened to the default iptables rules on the minimal install of CentOS6 x86_64
- Next by Date: Re: Socket behavior change from 6.5 to 6.6
- Previous by thread: Socket behavior change from 6.5 to 6.6
- Next by thread: Re: Socket behavior change from 6.5 to 6.6
- Index(es):
 |