After a bug report from Hamish, I did some reading to determine meaning of MSG_TRUNC for TCP sockets. I'd appreciate confirmation that the following text, scheduled the tcp(7) page in man-pages-3.15, matches reality, and the developers' intentions (but I am not sure who implemented this piece). Since version 2.4, Linux supports the use of MSG_TRUNC in the flags argument of recv(2) (and recvmsg(2)). This flag causes the received bytes of data to be discarded, rather than passed back in a caller-supplied buffer. Since Linux 2.4.4, MSG_PEEK also has this effect when used in conjunction with MSG_OOB to receive out-of-band data. Cheers, Michael -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html