Hi,
Just curious if the socket bug fixed in 2.2.17 was
related to getting a return of -1 on a socket recv().
I'm using the Red Hat 2.2.16-3 kernel and I'm getting
a return of -1 on a TCP recv() with flags set to 0.
(This should behave the same as a read() right?)
Although when I check the errno, it's 0. I'm a TCP server
and the client is a HP Jornada running M$ PocketPC (WinCE v3.0).
Is this the bug?
Thanks,
Tuan
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 21:00:33 EST