From: tym@dibbler.cs.monash.edu.au (Tim MacKenzie) Subject: Re: [Q] Bug in select(2)? Date: Fri, 18 Dec 1992 14:48:31 GMT
The Wyvern (wyvern@gnu.ai.mit.edu) wrote:
>I've also been noticing some strange behavior which seems to be also due to
>select(2), although it doesn't seem to be of the same type as mentioned
>above. I'm running a client/server program that uses sockets of type AF_INET.
>Up until 0.99 I wasn't having problems but now clients and servers are getting
>stuck. They just hang. ps -l shows the WCHAN for the hung processes as
>tcp_read
>when normally it shows do_select when they're working correctly. The programs
The way in which the tcp code does select has been changed recently.... I would
recommend getting the latest tcp and testing your code with that. The current
version (which is working well for me at the moment, except for asyncronous
connect's which can be fixed with a simple patch) is 0.99pl0 p5. This is
available in tsx-11.mit.edu:pub/linux/packages/tcpip/tcp99pl0-p5.Z
This patch is for 0.99 plain. You do not need 0.99pl0 patches 1-4.
I've tacked on Ross's tcp99pl0-p5.README