System Call Interruption
Posted Mar 31, 2006 15:23 UTC (Fri) by hppnq
In reply to: System Call Interruption
Parent article: The new pselect() system call
Portability is not an issue when your system call is actually interrupted. :-)
The complexity that arises from mixing signals and threads is only justified if you have specific reasons to implement it like that. By default, a multi-threaded process acts the same as a non-threaded process when interrupted.
So, unless you have specific reasons for defining per-thread signal masks (which is possible), there's nothing special about the multi-threaded case.
to post comments)