Re: select says I can read, but recvfrom hangs

[Andi Kleen <ak@xxxxxx>]

On Thu, Jun 21, 2001 at 05:31:49PM +0200, D. Hugh Redelmeier wrote:
> On Wed, 20 Jun 2001, Ben Greear wrote:
> 
> | From: Ben Greear <greearb@xxxxxxxxxxxxxxx>
> 
> | Make your socket O_NONBLOCKing, and you don't have to worry about that
> | kind of thing (just be sure you handle all the error cases, ie read
> | no data) correctly.
> |
> | I always just consider select() a hint, not the Truth :)
> 
> Of course that is a way to work arround a bug (if that is what I'm
> seeing), but it should not be necessary.  The specs for select say
> nothing about it being just a hint.

It is a hint when multiple processes access the same socket. When that's
not the case it would be a kernel bug. Because no such bugs are known
(and such things tend to get noticed) I would suspect the freeswan kernel
patches.



-Andi