From: Andries.Brouwer@cwi.nl
To: linux-kernel@vger.kernel.org
Subject: syscall documentation (3)
Date: Thu, 6 Feb 2003 21:09:24 +0100 (MET) [thread overview]
Message-ID: <UTC200302062009.h16K9Op23604.aeb@smtp.cwi.nl> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
The next new page is tkill.2
Comments welcome.
Andries
aeb@cwi.nl
-----------------------------------
NAME
tkill - send a signal to a single process
SYNOPSIS
#include <sys/types.h>
#include <linux/unistd.h>
_syscall2(int, tkill, pid_t, tid, int, sig)
int tkill(pid_t tid, int sig);
DESCRIPTION
The tkill system call is analogous to kill(2), except when
the specified process is part of a thread group (created
by specifying the CLONE_THREAD flag in the call to clone).
Since all the processes in a thread group have the same
PID, they cannot be individually signalled with kill.
With tkill, however, one can address each process by its
unique TID.
RETURN VALUE
On success, zero is returned. On error, -1 is returned,
and errno is set appropriately.
ERRORS
EINVAL An invalid TID or signal was specified.
ESRCH No process with the specified TID exists.
EPERM The caller did not have permission to send the sig
nal to the specified process. For a process to be
allowed to send a signal, it must either have root
privileges, or its real or effective user ID must
be equal to the real or saved set-user-ID of the
receiving process.
CONFORMING TO
tkill is Linux specific and should not be used in programs
that are intended to be portable.
SEE ALSO
gettid(2), kill(2)
Linux 2.4.20 2003-02-01 TKILL(2)
next reply other threads:[~2003-02-06 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 20:09 Andries.Brouwer [this message]
2003-02-06 20:52 ` Christoph Hellwig
2003-02-06 21:11 Andries.Brouwer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=UTC200302062009.h16K9Op23604.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®