nl_connect EADDRINUSE error after child is forked

[Andrew]

Thomas,
I confirmed that version 3.2.25 of libnl does address this issue.
Thanks again,
- Andrew

----------------------------------------
> From: andykras at hotmail.com
> To: thaller at redhat.com
> CC: libnl at lists.infradead.org
> Subject: RE: nl_connect EADDRINUSE error after child is forked
> Date: Fri, 1 Aug 2014 09:26:17 -0700
>
> Thomas,
> Thanks! That definitely looks like it will take care of the problem I am seeing.
> I will give it a try and let you know the results.
> - Andrew
>
> ----------------------------------------
>> Subject: Re: nl_connect EADDRINUSE error after child is forked
>> From: thaller at redhat.com
>> To: andykras at hotmail.com
>> CC: libnl at lists.infradead.org
>> Date: Fri, 1 Aug 2014 02:38:20 +0200
>>
>> On Thu, 2014-07-31 at 16:32 -0700, Andrew wrote:
>>> [Re-send, hopefully with legible formatting]
>>
>> it's slightly better ;-)
>>
>>
>>
>>
>>
>>> 2) Implement a "best effort" auto-bind in libnl.
>>
>>> Basically, instead of giving up when socket() returns EADDRINUSE on the first available
>>
>>> port, try each port marked in the pool as available until the socket() call succeeds or
>>
>>> an error other than EADDRINUSE is returned.
>>
>>
>> Yes, this was done upstream, see
>> https://github.com/thom311/libnl/commit/4dd5fdd0af2c0b7ffe1dbc49313f263dbb2e906f .
>>
>>
>> Try to upgrade to version 3.2.25, or backport this commit.
>>
>> Possibly you want to backport all 4 commits that were merged with
>> https://github.com/thom311/libnl/commit/e21099908f6e22d869b2b8eeb1ffbcc2eff209e4 .
>>
>>
>>
>> Does that solve your issue?
>> Thomas
>>
>>
>