Provided by: manpages-dev_3.27-1ubuntu2_all
siginterrupt - allow signals to interrupt system calls
int siginterrupt(int sig, int flag);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
Since glibc 2.12
_BSD_SOURCE || _XOPEN_SOURCE >= 500 || _XOPEN_SOURCE &&
_XOPEN_SOURCE_EXTENDED || _POSIX_C_SOURCE >= 200809L ||
_XOPEN_SOURCE >= 700
Before glibc 2.12
_BSD_SOURCE || _XOPEN_SOURCE >= 500 ||
_XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED
The siginterrupt() function changes the restart behavior when a system
call is interrupted by the signal sig. If the flag argument is false
(0), then system calls will be restarted if interrupted by the
specified signal sig. This is the default behavior in Linux. However,
when a new signal handler is specified with the signal(2) function, the
system call is interrupted by default.
If the flag argument is true (1) and no data has been transferred, then
a system call interrupted by the signal sig will return -1 and errno
will be set to EINTR.
If the flag argument is true (1) and data transfer has started, then
the system call will be interrupted and will return the actual amount
of data transferred.
The siginterrupt() function returns 0 on success, or -1 if the signal
number sig is invalid.
EINVAL The specified signal number is invalid.
4.3BSD, POSIX.1-2001. POSIX.1-2008 marks siginterrupt() as obsolete,
recommending the use of sigaction(2) with the SA_RESTART flag instead.
This page is part of release 3.27 of the Linux man-pages project. A
description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.