Re: connect() returns EADDRINUSE during massive host->host conn rate
- From: Jan Srzednicki <w@xxxxxxxxx>
- Date: Wed, 28 Nov 2007 19:17:25 +0100
On Tue, Nov 27, 2007 at 02:53:20PM +0100, Jan Srzednicki wrote:
Hello,
setting up the relevant fields, setting SO_REUSEADDR and SO_KEEPALIVE,
setting O_NONBLOCK on the descriptor. No bind(2) is performed. The
connection is initiated from inside a jail (not sure if that implies a
internal bind(2) to the jail's address). There are no connections from
the other host to the first one.
And some additional info: subsequent connect()s on the same keep
returning EADDRINUSE as well. In order to establish a connection, the
application must create a brand new socket and then retry connect().
--
Jan Srzednicki :: http://wrzask.pl/
"Remember, remember, the fifth of November"
-- V for Vendetta
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"
- References:
- connect() returns EADDRINUSE during massive host->host conn rate
- From: Jan Srzednicki
- connect() returns EADDRINUSE during massive host->host conn rate
- Prev by Date: [releng_6 tinderbox] failure on sparc64/sparc64
- Next by Date: Re: connect() returns EADDRINUSE during massive host->host conn rate
- Previous by thread: connect() returns EADDRINUSE during massive host->host conn rate
- Next by thread: Re: connect() returns EADDRINUSE during massive host->host conn rate
- Index(es):
Relevant Pages
|
|
