killpg - Send a signal to a process group
int signal );
Application developers may want to specify an #include
statement for <sys/types.h> before the one for <signal.h>
if programs are being developed for multiple platforms.
The additional #include statement is not required on Tru64
UNIX systems or by ISO or XSH standards, but may be on
other vendors' systems that conform to these standards.
Interfaces documented on this reference page conform to
industry standards as follows:
killpg(): XSH4.2, XSH5.0
Refer to the standards(5) reference page for more information
about industry standards and associated tags.
Specifies the process group. Specifies the signal. If
the signal parameter is a value of 0 (zero, the null signal),
error checking is performed but no signal is sent.
This parameter can be used to check the validity of the
The killpg() function sends the signal specified by the
signal parameter to the group of processes specified by
the process_grp parameter.
The process sending the signal must have the same effective
user ID or saved set-user-ID as the members of the
process group, or the sending process must belong to the
superuser. The continue signal, SIGCONT, is a special
case: it may be sent to any process that is a descendent
of the current process.
Upon successful completion, the killpg() function returns
a value of 0 (zero). Otherwise, a value of -1 is returned,
and errno is set to indicate the error.
If any of the following conditions occurs, the killpg()
function sets errno to the corresponding value: The signal
parameter is not a valid signal number. No process can be
found in process_grp.
[Tru64 UNIX] The process group was given as 0
(zero), but the sending process does not have a
process group. The real or saved user ID does not
match the real or effective user ID of the receiving
process, the calling process does not have the
appropriate privilege, and the process is not
sending a SIGCONT signal to one of its session's
Functions: getpid(2), kill(2), setpgid(2), sigaction(2),
[ Back ]