Nicolas Cannasse a écrit :
If there is data and the thread didn't wake up then that is a libc or
kernel problem;
but if there is no data, then look for cases where earlier
interrupted io actually
consumed the data already or blame the sending process not the receiver.
Also are the sockets blocking or non-blocking?
One other thing :
We tried to use a poll(POLLIN) on the socket before entering the recv().
The poll() does exit (and we are looping in case of EINTR result) but
after that recv() blocks infinitely.
Hope that helps,
Nicolas
--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
