Messages in this thread |  | | From | (Alan Cox) | Subject | Re: Lynx spinning. Kernel problem? | Date | Mon, 25 Nov 1996 19:32:14 +0000 (GMT) |
| |
> So what I imagine is happening is lynx (2.3 BETA) calls 'connect' > with a non-blocking socket, and connect returns immediately. Then lynx > selects with a zero timeout, the select returns, and lynx calls connect > again. But why would lynx do anything so stupid?
Lynx is written by folks who didnt read the man pages to select carefully. Make it reassign a timeout to the select before each select call
Alan
|  |