icon Top 9 categories map      RocketAware > man pages >


Tips: Browse or Search all pages for efficient awareness of more than 6000 of the most popular reusable and open source applications, functions, libraries, and FAQs.

The "RKT couplings" below include links to source code, updates, additional information, advice, FAQs, and overviews.


Search all pages


By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Integer, Floating point, Matrix, Statistics, Boolean, ...

Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...


RocketLink!--> Man page versions: OpenBSD FreeBSD RedHat Others

SIGINTERRUPT(3)           OpenBSD Programmer's Manual          SIGINTERRUPT(3)

     siginterrupt - allow signals to interrupt system calls

     #include <signal.h>

     siginterrupt(int sig, int flag);

     The siginterrupt() function is used to change the system call restart be-
     havior when a system call is interrupted by the specified signal.  If
     flag is false (0), system calls will be restarted if they are interrupted
     by the specified signal sig and no data has been transferred yet.  System
     call restart is the default behavior on 4.2BSD.

     If flag is true (1), the restarting of system calls is disabled.  If a
     system call is interrupted by the specified signal and no data has been
     transferred, the system call will return -1 with the global variable
     errno set to EINTR. Interrupted system calls that have started transfer-
     ring data will return the amount of data actually transferred.  System
     call interrupt is the signal behavior found on 4.1BSD and AT&T System V
     UNIX systems.

     Note that the new 4.2BSD signal handling semantics are not altered in any
     other way.  Most notably, signal handlers always remain installed until
     explicitly changed by a subsequent sigaction(2) call, and the signal mask
     operates as documented in sigaction(2).  Programs may switch between
     restartable and interruptible system call operation as often as desired
     in the execution of a program.

     Issuing a siginterrupt() call during the execution of a signal handler
     will cause the new action to take place on the next signal to be caught.

     This library routine uses an extension of the sigaction(2) system call
     that is not available in 4.2BSD, hence it should not be used if backward
     compatibility is needed.

     siginterrupt() returns 0 on success or -1 if an invalid signal number has
     been specified.

     sigaction(2),  sigblock(3),  sigpause(3),  sigsetmask(3)

     The siginterrupt() function appeared in 4.3BSD.

OpenBSD 2.6                      June 4, 1993                                1

Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.

(Corrections, notes, and links courtesy of RocketAware.com)

[Detailed Topics]
FreeBSD Sources for siginterrupt(3) functions
OpenBSD sources for siginterrupt(3)

[Overview Topics]

Up to: Process Signals and Events - Sending and handling signals and events.

RocketLink!--> Man page versions: OpenBSD FreeBSD RedHat Others

Rapid-Links: Search | About | Comments | Submit Path: RocketAware > man pages > siginterrupt.3/
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments