Stop me if you've heard this one before.
We're using a very old epoll patch (ep_patch-2.4.18-0.32),
and have noticed that if there is a dropped TCP packet
followed by a FIN, epoll says the socket is ready for
POLLHUP *before* all the data has been read from the socket.
As a workaround, we are ignoring POLLHUP and simply reading
until we get EOF; this solves the problem nicely.
Has this problem with epoll been solved in newer versions?
Thanks,
Dan
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
