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
