Using alarm(3) on background NSOperationQueue threads
Using alarm(3) on background NSOperationQueue threads
- Subject: Using alarm(3) on background NSOperationQueue threads
- From: Carl Hoefs <email@hidden>
- Date: Thu, 20 Aug 2015 17:29:04 -0700
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 there something inherent in NSOperationQueue that would block the delivery of alarms? Is there another way to effect this?
-Carl
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden