> On Aug 20, 2015, at 5:55 PM, Ken Thomases wrote:
>
> On Aug 20, 2015, at 7:29 PM, Carl Hoefs
> wrote:
>>
>> From within a background NSOperationQueue thread, the effects of alarm(3)
>> seem to be ignored. (I use alarm() to interrupt certain system calls like
>> connect() when they stall.)
On Aug 20, 2015, at 7:29 PM, Carl Hoefs wrote:
>
> From within a background NSOperationQueue thread, the effects of alarm(3)
> seem to be ignored. (I use alarm() to interrupt certain system calls like
> connect() when they stall.) The alarm fires, the alarm handler is invoked,
> but the ongoin
From within a background NSOperationQueue thread, the effects of alarm(3) seem
to be ignored. (I use alarm() to interrupt certain system calls like connect()
when they stall.) The alarm fires, the alarm handler is invoked, but the
ongoing sys call is not interrupted, as it would be normally. Is