diff options
| author | Richard Lowe <richlowe@richlowe.net> | 2022-02-01 16:25:34 -0600 |
|---|---|---|
| committer | Richard Lowe <richlowe@richlowe.net> | 2022-02-18 15:32:41 -0600 |
| commit | bb788c55f7450a1360e9752bf81c3a3932cc8018 (patch) | |
| tree | 77443122971496a73748e2d9722913303ab61b55 /usr/src/man/man3c/pthread_testcancel.3c | |
| parent | 7d5a0c32ad2a16518949e2843f208bf257e5cf79 (diff) | |
| download | illumos-joyent-bb788c55f7450a1360e9752bf81c3a3932cc8018.tar.gz | |
manual: fix up free-form normative manual references in the manual
Diffstat (limited to 'usr/src/man/man3c/pthread_testcancel.3c')
| -rw-r--r-- | usr/src/man/man3c/pthread_testcancel.3c | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/usr/src/man/man3c/pthread_testcancel.3c b/usr/src/man/man3c/pthread_testcancel.3c index 8d48f87b3e..527c5759ed 100644 --- a/usr/src/man/man3c/pthread_testcancel.3c +++ b/usr/src/man/man3c/pthread_testcancel.3c @@ -77,12 +77,12 @@ The \fBpthread_testcancel()\fR function does not return errors. .SH EXAMPLES .sp .LP -See \fBcancellation\fR(5) for an example of using \fBpthread_testcancel()\fR to +See \fBcancellation\fR(7) for an example of using \fBpthread_testcancel()\fR to force testing for cancellation and a discussion of cancellation concepts. .SH ATTRIBUTES .sp .LP -See \fBattributes\fR(5) for descriptions of the following attributes: +See \fBattributes\fR(7) for descriptions of the following attributes: .sp .sp @@ -103,8 +103,8 @@ MT-Level MT-Safe \fBIntro\fR(3), \fBpthread_cleanup_pop\fR(3C), \fBpthread_cleanup_push\fR(3C), \fBpthread_exit\fR(3C), \fBpthread_join\fR(3C), \fBpthread_setcancelstate\fR(3C), \fBpthread_setcanceltype\fR(3C), -\fBsetjmp\fR(3C), \fBattributes\fR(5), \fBcancellation\fR(5), -\fBcondition\fR(5), \fBstandards\fR(5) +\fBsetjmp\fR(3C), \fBattributes\fR(7), \fBcancellation\fR(7), +\fBcondition\fR(7), \fBstandards\fR(7) .SH NOTES .sp .LP @@ -122,5 +122,5 @@ to \fBPTHREAD_CANCEL_ASYNCHRONOUS\fR. It is possible to kill a thread when it is holding a resource, such as lock or allocated memory. If that thread has not setup a cancellation cleanup handler to release the held resource, the application is "cancel-unsafe". See -\fBattributes\fR(5) for a discussion of Cancel-Safety, Deferred-Cancel-Safety, +\fBattributes\fR(7) for a discussion of Cancel-Safety, Deferred-Cancel-Safety, and Asynchronous-Cancel-Safety. |