Re: [Libevent-users] missing EINTR handling?

[Pierre Phaneuf <pphaneuf@xxxxxxxxxx>]

On Wed, Oct 28, 2009 at 8:13 AM, Marko Kreen <markokr@xxxxxxxxx> wrote:

> Btw, this discussion seem to connect to the non-blocking discussion -
> looping on EINTR is safe on non-blocking sockets, but not on blocking
> ones, as there is chance to stall the app.

You'd still get a similar result to what you had in the first place
when you called write() on the blocking socket. When EINTR is
returned, no work has been done, so if you received a hint from
select()/poll()/other that there was enough space to write, the hint
is still "just as good" (which might be "not at all", of course, but
this is the normal situation).
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.