1 .\" Copyright (c) 2002, 2011 Michael Kerrisk <mtk.manpages@gmail.com>
3 .\" %%%LICENSE_START(VERBATIM)
4 .\" Permission is granted to make and distribute verbatim copies of this
5 .\" manual provided the copyright notice and this permission notice are
6 .\" preserved on all copies.
8 .\" Permission is granted to copy and distribute modified versions of this
9 .\" manual under the conditions for verbatim copying, provided that the
10 .\" entire resulting derived work is distributed under the terms of a
11 .\" permission notice identical to this one.
13 .\" Since the Linux kernel and libraries are constantly changing, this
14 .\" manual page may be incorrect or out-of-date. The author(s) assume no
15 .\" responsibility for errors or omissions, or for damages resulting from
16 .\" the use of the information contained herein. The author(s) may not
17 .\" have taken the same level of care in the production of this manual,
18 .\" which is licensed free of charge, as they might when working
21 .\" Formatted or processed versions of this manual, if unaccompanied by
22 .\" the source, must acknowledge the copyright and authors of this work.
25 .TH RT_SIGQUEUEINFO 2 2017-09-15 "Linux" "Linux Programmer's Manual"
27 rt_sigqueueinfo, rt_tgsigqueueinfo \- queue a signal and data
30 .BI "int rt_sigqueueinfo(pid_t " tgid ", int " sig ", siginfo_t *" uinfo );
32 .BI "int rt_tgsigqueueinfo(pid_t " tgid ", pid_t " tid ", int " sig ,
33 .BI " siginfo_t *" uinfo );
37 There are no glibc wrappers for these system calls; see NOTES.
40 .BR rt_sigqueueinfo ()
42 .BR rt_tgsigqueueinfo ()
43 system calls are the low-level interfaces used to send a signal plus data
44 to a process or thread.
45 The receiver of the signal can obtain the accompanying data
46 by establishing a signal handler with the
51 These system calls are not intended for direct application use;
52 they are provided to allow the implementation of
55 .BR pthread_sigqueue (3).
58 .BR rt_sigqueueinfo ()
59 system call sends the signal
61 to the thread group with the ID
63 (The term "thread group" is synonymous with "process", and
65 corresponds to the traditional UNIX process ID.)
66 The signal will be delivered to an arbitrary member of the thread group
67 (i.e., one of the threads that is not currently blocking the signal).
71 argument specifies the data to accompany the signal.
72 This argument is a pointer to a structure of type
76 (and defined by including
78 The caller should set the following fields in this structure:
81 This must be one of the
83 codes in the Linux kernel source file
84 .IR include/asm-generic/siginfo.h ,
85 with the restriction that the code must be negative
88 which is used by the kernel to indicate a signal sent by
90 and cannot (since Linux 2.6.39) be
92 (which is used by the kernel to indicate a signal sent using
97 This should be set to a process ID,
98 typically the process ID of the sender.
101 This should be set to a user ID,
102 typically the real user ID of the sender.
105 This field contains the user data to accompany the signal.
106 For more information, see the description of the last
107 .RI ( "union sigval" )
111 Internally, the kernel sets the
113 field to the value specified in
115 so that the receiver of the signal can also obtain
116 the signal number via that field.
119 .BR rt_tgsigqueueinfo ()
121 .BR rt_sigqueueinfo (),
122 but sends the signal and data to the single thread
123 specified by the combination of
128 a thread in that thread group.
130 On success, these system calls return 0.
131 On error, they return \-1 and
133 is set to indicate the error.
137 The limit of signals which may be queued has been reached.
140 for further information.)
150 The caller does not have permission to send the signal to the target.
151 For the required permissions, see
158 .BR rt_sigqueueinfo ():
159 No thread group matching
163 .BR rt_tgsigqueinfo ():
171 .BR rt_sigqueueinfo ()
172 system call was added to Linux in version 2.2.
174 .BR rt_tgsigqueueinfo ()
175 system call was added to Linux in version 2.6.31.
177 These system calls are Linux-specific.
179 Since these system calls are not intended for application use,
180 there are no glibc wrapper functions; use
182 in the unlikely case that you want to call them directly.
186 the null signal (0) can be used to check if the specified process
193 .BR pthread_sigqueue (3),