from small one page howto to huge articles all in one place
 

search text in:





Poll
What does your sytem tell when running "ulimit -u"?








poll results

Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

186359

userrating:

average rating: 1.7 (102 votes) (1=very good 6=terrible)


May 25th. 2007:
Words

486

Views

250360

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

137537

userrating:

average rating: 1.4 (42 votes) (1=very good 6=terrible)


April, 26th. 2006:

Druckversion
You are here: manpages





KILLPG

Section: Linux Programmer's Manual (3)
Updated: 2017-09-15
Index Return to Main Contents
 

NAME

killpg - send signal to a process group  

SYNOPSIS

#include <signal.h>

int killpg(int pgrp, int sig);

Feature Test Macro Requirements for glibc (see feature_test_macros(7)):

killpg():
_XOPEN_SOURCE >= 500
    || /* Since glibc 2.19: */ _DEFAULT_SOURCE
    || /* Glibc versions <= 2.19: */ _BSD_SOURCE
 

DESCRIPTION

killpg() sends the signal sig to the process group pgrp. See signal(7) for a list of signals.

If pgrp is 0, killpg() sends the signal to the calling process's process group. (POSIX says: if pgrp is less than or equal to 1, the behavior is undefined.)

For the permissions required to send a signal to another process, see kill(2).  

RETURN VALUE

On success, zero is returned. On error, -1 is returned, and errno is set appropriately.  

ERRORS

EINVAL
sig is not a valid signal number.
EPERM
The process does not have permission to send the signal to any of the target processes. For the required permissions, see kill(2).
ESRCH
No process can be found in the process group specified by pgrp.
ESRCH
The process group was given as 0 but the sending process does not have a process group.
 

CONFORMING TO

POSIX.1-2001, POSIX.1-2008, SVr4, 4.4BSD (killpg() first appeared in 4BSD).  

NOTES

There are various differences between the permission checking in BSD-type systems and System V-type systems. See the POSIX rationale for kill(). A difference not mentioned by POSIX concerns the return value EPERM: BSD documents that no signal is sent and EPERM returned when the permission check failed for at least one target process, while POSIX documents EPERM only when the permission check failed for all target processes.  

C library/kernel differences

On Linux, killpg() is implemented as a library function that makes the call kill(-pgrp, sig).  

SEE ALSO

getpgrp(2), kill(2), signal(2), capabilities(7), credentials(7)  

COLOPHON

This page is part of release 4.13 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.


 

Index

NAME
SYNOPSIS
DESCRIPTION
RETURN VALUE
ERRORS
CONFORMING TO
NOTES
C library/kernel differences
SEE ALSO
COLOPHON





Support us on Content Nation
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2020 Sascha Nitsch Unternehmensberatung GmbH
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 17.2 ms