Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: bind address lockup
From: Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>
Date: Thu, 27 Jun 2019 23:38:48 +0200 (CEST)
Date: Thu, 27 Jun 2019 23:38:48 +0200 (CEST)
On Thu, 27 Jun 2019, Robert NEMKIN wrote:
> Hope I'm right, but bind() is for server/receiving sockets. I want to bind
> to a specific interface as client socket.
It's the same bind() call. No setsockopt for this.
> I know, that setsockopt is thread safe according to the POSIX standard. But
> is the linux kernel (4.19.37-5) implementation correct?
This isn't using setsockopt, this is bind.
> Sometimes it took more than a minute to start the transfer, sometimes it
> never starts.
That certainly indicates something odd!
--
/ daniel.haxx.se | Get the best commercial curl support there is - from me
| Private help, bug fixes, support, ports, new features
| https://www.wolfssl.com/contact/
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2019-06-27