diff options
author | Michael Kerrisk <mtk.manpages@gmail.com> | 2016-12-05 10:38:53 +0100 |
---|---|---|
committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2016-12-05 16:51:15 +0100 |
commit | f793f8bc91eb39179cd9f010aaf3069ba58742a7 (patch) | |
tree | 16c69d18222106c1310b57aad4bf2ee8d1916262 | |
parent | 3d463c677e773373d2dd59f52d9109b05b36bb08 (diff) | |
download | util-linux-f793f8bc91eb39179cd9f010aaf3069ba58742a7.tar.gz |
docs: kill(1): Rework notes on thread groups
The points in the NOTES can be expressed more compactly
(there is some redundancy in the two existing paragraphs).
Also, add a reference to signal(7), since this provides
much more detail on the topic.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r-- | misc-utils/kill.1 | 33 |
1 files changed, 15 insertions, 18 deletions
diff --git a/misc-utils/kill.1 b/misc-utils/kill.1 index 091de407d3..1d7e765521 100644 --- a/misc-utils/kill.1 +++ b/misc-utils/kill.1 @@ -117,25 +117,22 @@ flag to then it can obtain this data via the si_sigval field of the siginfo_t structure. .SH NOTES -It is not possible to send a signal to an explicitly selected thread in a -multithreaded process using the -.BR kill (2) -system call. If -.BR kill (2) -is used to send a signal to a thread group, then the kernel selects an arbitrary -member of the thread group that has not blocked the signal. For more details -see -.BR clone (2), -the CLONE_THREAD description. -.PP -The command -.BR kill (1) -as well as system call -.BR kill (2) -accept a TID (thread ID, see +Although it is possible to specify the TID (thread ID, see .BR gettid (2)) -as an argument. In this case the kill behavior is not changed and the signal is -also delivered to the thread group rather than to the specified thread. +of one of the threads in a multithreaded process as the argument of +.BR kill , +the signal is nevertheless directed to the process +(i.e., the entire thread group). +In other words, it is not possible to send a signal to an +explicitly selected thread in a multithreaded process. +The signal will be delivered to an arbitrarily selected thread +in the target process that is not blocking the signal. +For more details, see +.BR signal (7) +and the description of +.BR CLONE_THREAD +in +.BR clone (2). .SH RETURN CODES .B kill |