the UDP socket option should be using non-block mode which need to not take
EAGAIN return value for read/write as an error. it means 'no socket buffer
for now, please try again later' for write UDP, or 'no packet received yet
in the buffer' for read.
solution: for write, please set socket option to
2013/8/26 Edwin Mons
> Is anyone already looking into this?
>
Not that I've heard of (the last couple of years.)
--
Tommie
Hi,
We're using C-ARES to do DNS resolving in our products. During high network
load, we hit an issue in ares_process.c:785 where writing to a UDP socket on
Linux fails with an EAGAIN error. The FIXME comment in the code suggests this
could happen, but it is as of yet left unresolved.
Part o
