des_crypt.3: Minor wording fix in VERSIONS

[thirdparty/man-pages.git] / man3 / bsd_signal.3

diff --git a/man3/bsd_signal.3 b/man3/bsd_signal.3
index 30004632f24841a0377e7921fe37baf2986ed050..43aa5ac31784dacbdebbe5535588d4b41ef2147f 100644 (file)
--- a/man3/bsd_signal.3
+++ b/man3/bsd_signal.3
@@ -22,7 +22,7 @@
 .\" the source, must acknowledge the copyright and authors of this work.
 .\" %%%LICENSE_END
 .\"
-.TH BSD_SIGNAL 3 2017-07-13 "" "Linux Programmer's Manual"
+.TH BSD_SIGNAL 3 2019-03-06 "" "Linux Programmer's Manual"
 .SH NAME
 bsd_signal \- signal handling with BSD semantics
 .SH SYNOPSIS
@@ -43,7 +43,7 @@ Feature Test Macro Requirements for glibc (see
 Since glibc 2.26:
     _XOPEN_SOURCE >= 500
 .\"    || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED
-        && ! (_POSIX_C_SOURCE\ >=\ 200112L)
+        && ! (_POSIX_C_SOURCE\ >=\ 200809L)
 .br
 Glibc 2.25 and earlier:
     _XOPEN_SOURCE
@@ -54,7 +54,7 @@ The
 .BR bsd_signal ()
 function takes the same arguments, and performs the same task, as
 .BR signal (2).
-
+.PP
 The difference between the two is that
 .BR bsd_signal ()
 is guaranteed to provide reliable signal semantics, that is:
@@ -101,7 +101,7 @@ Use of
 should be avoided; use
 .BR sigaction (2)
 instead.
-
+.PP
 On modern Linux systems,
 .BR bsd_signal ()
 and
@@ -112,7 +112,7 @@ But on older systems,
 provided unreliable signal semantics; see
 .BR signal (2)
 for details.
-
+.PP
 The use of
 .I sighandler_t
 is a GNU extension;