> To the best of my knowledge, connect() being always interruptable
> is correct and well-known.
Fair enough, that answers my question!
> And my 4.11-STABLE system will interrupt connect() on a signal with
> SA_RESTART set, which disagrees with your observations yet agrees with
> the standard. P
On Wed, Feb 01, 2006 at 08:48:30PM +, Pete French wrote:
> > >>I have a piece of coode which does some networking, in which I see read
> > >>and write calls failing with 'Interrupted system call' from time to time.
> > >
> > > You will get EINTR if the interrupt occurs before any data is read
> >>I have a piece of coode which does some networking, in which I see read
> >>and write calls failing with 'Interrupted system call' from time to time.
> >
> > You will get EINTR if the interrupt occurs before any data is read
> > or written.
>
> Will it also happen with recv() with MSG_WAITALL
Peter Jeremy wrote:
On Wed, 2006-Feb-01 11:44:08 +, Pete French wrote:
I have a piece of coode which does some networking, in which I see read
and write calls failing with 'Interrupted system call' from time to time.
You will get EINTR if the interrupt occurs before any data is read
or wr
On Wed, 2006-Feb-01 11:44:08 +, Pete French wrote:
>I have a piece of coode which does some networking, in which I see read
>and write calls failing with 'Interrupted system call' from time to time.
You will get EINTR if the interrupt occurs before any data is read
or written.
--
Peter Jerem
I have a piece of coode which does some networking, in which I see read
and write calls failing with 'Interrupted system call' from time to time.
The reason it puzzles me is that I am explicitly catching every signal
that could possibly be causing this, with the SA_RESTART flag set. So
surely I sh
