aboutsummaryrefslogtreecommitdiffstats
path: root/man7
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2019-10-05 14:40:52 +0300
committerMichael Kerrisk <mtk.manpages@gmail.com>2019-10-05 14:54:15 +0300
commit50639a2a18a4670a4c0055569bfbb59492ce3dc4 (patch)
treec72631fbfc34008b03667165f2bd731f81e33e1a /man7
parentdbb01cbbdb60c34a16d9d48cb58ed3680a5dd36d (diff)
downloadman-pages-50639a2a18a4670a4c0055569bfbb59492ce3dc4.tar.gz
pthread_setcancelstate.3, pthreads.7: srcfix: wrap source lines at sentence boundaries
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man7')
-rw-r--r--man7/pthreads.76
1 files changed, 4 insertions, 2 deletions
diff --git a/man7/pthreads.7 b/man7/pthreads.7
index b39236c398..aa56589432 100644
--- a/man7/pthreads.7
+++ b/man7/pthreads.7
@@ -569,9 +569,11 @@ any nonstandard function that may block as a cancellation point.
It should be noted that even if an application is not using
asynchronous cancellation, that calling a function from the above list
from an asynchronous signal handler may cause the equivalent of
-asynchronous cancellation. The underlying user code may not expect
+asynchronous cancellation.
+The underlying user code may not expect
asynchronous cancellation and the state of the user data may become
-inconsistent. Therefore signals should be used with caution when
+inconsistent.
+Therefore signals should be used with caution when
entering a region of deferred cancellation.
.\" So, scanning "cancellation point" comments in the glibc 2.8 header
.\" files, it looks as though at least the following nonstandard