Re: Stop signals and interruption of system calls on Linux

[Manfred Spraul <yyyyyyy@xxxxxxxxxxxxxxxx>]

Hi David,

Quoting your old comp.std.unix posting:

> However, see subclause 3.3.1.4, which describes the effects of signals
> on other functions, and contains:
>
>    If the action of the signal is to invoke a signal-catching
>    function, ... the original function is said to be *interrupted* by
>    the signal.
>
> This, and other wording in 3.3.1.4 makes it clear, I think, that the
> bit about EINTR in the description of read() does not apply to job
> control signals that were not caught.
>  
Does that mean that signals that are not delivered to user space should 
never cause a syscall to return with -1, errno=EINTR?

--
   Manfred