|
HTML rendering created 2024-06-26 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|
|
NAME | LIBRARY | SYNOPSIS | DESCRIPTION | RETURN VALUE | ERRORS | ATTRIBUTES | VERSIONS | STANDARDS | HISTORY | SEE ALSO | COLOPHON |
|
|
|
bsd_signal(3) Library Functions Manual bsd_signal(3)
bsd_signal - signal handling with BSD semantics
Standard C library (libc, -lc)
#include <signal.h>
typedef void (*sighandler_t)(int);
sighandler_t bsd_signal(int signum, sighandler_t handler);
Feature Test Macro Requirements for glibc (see
feature_test_macros(7)):
bsd_signal():
Since glibc 2.26:
_XOPEN_SOURCE >= 500
&& ! (_POSIX_C_SOURCE >= 200809L)
glibc 2.25 and earlier:
_XOPEN_SOURCE
The bsd_signal() function takes the same arguments, and performs
the same task, as signal(2).
The difference between the two is that bsd_signal() is guaranteed
to provide reliable signal semantics, that is: a) the disposition
of the signal is not reset to the default when the handler is
invoked; b) delivery of further instances of the signal is
blocked while the signal handler is executing; and c) if the
handler interrupts a blocking system call, then the system call
is automatically restarted. A portable application cannot rely
on signal(2) to provide these guarantees.
The bsd_signal() function returns the previous value of the
signal handler, or SIG_ERR on error.
As for signal(2).
For an explanation of the terms used in this section, see
attributes(7).
┌─────────────────────────────────────┬───────────────┬─────────┐
│ Interface │ Attribute │ Value │
├─────────────────────────────────────┼───────────────┼─────────┤
│ bsd_signal() │ Thread safety │ MT-Safe │
└─────────────────────────────────────┴───────────────┴─────────┘
Use of bsd_signal() should be avoided; use sigaction(2) instead.
On modern Linux systems, bsd_signal() and signal(2) are
equivalent. But on older systems, signal(2) provided unreliable
signal semantics; see signal(2) for details.
The use of sighandler_t is a GNU extension; this type is defined
only if the _GNU_SOURCE feature test macro is defined.
None.
4.2BSD, POSIX.1-2001. Removed in POSIX.1-2008, recommending the
use of sigaction(2) instead.
sigaction(2), signal(2), sysv_signal(3), signal(7)
This page is part of the man-pages (Linux kernel and C library
user-space interface documentation) project. Information about
the project can be found at
⟨https://www.kernel.org/doc/man-pages/⟩. If you have a bug report
for this manual page, see
⟨https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING⟩.
This page was obtained from the tarball man-pages-6.9.1.tar.gz
fetched from
⟨https://mirrors.edge.kernel.org/pub/linux/docs/man-pages/⟩ on
2024-06-26. If you discover any rendering problems in this HTML
version of the page, or you believe there is a better or more up-
to-date source for the page, or you have corrections or
improvements to the information in this COLOPHON (which is not
part of the original manual page), send a mail to
man-pages@man7.org
Linux man-pages 6.9.1 2024-05-02 bsd_signal(3)
Pages that refer to this page: signal(2), sysv_signal(3), signal(7)
|
HTML rendering created 2024-06-26 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|