From: Alan Cox <[EMAIL PROTECTED]> Date: Tue, 16 Aug 2005 15:03:11 +0100
> You are describing behaviour as expected with nonblocking set. That > suggests to me that something or someone set or inherited the nonblock > flag on that socket. Is the strange behaviour specific to the latest > kernel ? He could be receiving a signal Alan, look at tcp_recvmsg(), it returns -EAGAIN and always has when a signal is delivered to the reading process. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
