From 3af6d22bb3850ab2bac67287e3a3d3b0e32868e5 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Mon, 15 Apr 2024 21:41:07 +0200 Subject: Merging upstream version 6.7. Signed-off-by: Daniel Baumann --- man3/bsd_signal.3 | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) (limited to 'man3/bsd_signal.3') diff --git a/man3/bsd_signal.3 b/man3/bsd_signal.3 index 3294c5c..19c2147 100644 --- a/man3/bsd_signal.3 +++ b/man3/bsd_signal.3 @@ -3,7 +3,7 @@ .\" .\" SPDX-License-Identifier: Linux-man-pages-copyleft .\" -.TH bsd_signal 3 2023-07-20 "Linux man-pages 6.05.01" +.TH bsd_signal 3 2023-10-31 "Linux man-pages 6.7" .SH NAME bsd_signal \- signal handling with BSD semantics .SH LIBRARY @@ -12,17 +12,17 @@ Standard C library .SH SYNOPSIS .nf .B #include -.PP +.P .B typedef void (*sighandler_t)(int); -.PP +.P .BI "sighandler_t bsd_signal(int " signum ", sighandler_t " handler ); .fi -.PP +.P .RS -4 Feature Test Macro Requirements for glibc (see .BR feature_test_macros (7)): .RE -.PP +.P .BR bsd_signal (): .nf Since glibc 2.26: @@ -37,7 +37,7 @@ The .BR bsd_signal () function takes the same arguments, and performs the same task, as .BR signal (2). -.PP +.P The difference between the two is that .BR bsd_signal () is guaranteed to provide reliable signal semantics, that is: @@ -73,14 +73,13 @@ T{ .BR bsd_signal () T} Thread safety MT-Safe .TE -.sp 1 .SH VERSIONS Use of .BR bsd_signal () should be avoided; use .BR sigaction (2) instead. -.PP +.P On modern Linux systems, .BR bsd_signal () and @@ -91,7 +90,7 @@ But on older systems, provided unreliable signal semantics; see .BR signal (2) for details. -.PP +.P The use of .I sighandler_t is a GNU extension; -- cgit v1.2.3