From: Chris Newport <crn@xxxxxxxxxxx> Date: Thu, 29 Jun 2006 22:37:08 +0100 > I could be wrong, but there seem to be generic issues running tftpd via > inetd, often only intermittently reproduceable. It reproduces only when tftpd is invoked from inetd before the client sends out the first packet. If inetd gets a non-blocking socket, it chokes on the first read() when data is not available in the socket receive buffer. If the client is fast enough, or the tftpd server slow enough, this will never happen. That's why it might be intermittently reproducable. Believe me, I traced this one down to the source :) - To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
