DataMuseum.dk

Presents historical artifacts from the history of:

ICL Comet 32

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about ICL Comet 32

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - metrics - download

⟦2fe0fb2af⟧ TextFile

    Length: 1765 (0x6e5)
    Types: TextFile
    Notes: UNIX file
    Names: »killpg.2j«

Derivation

└─⟦26887b7e0⟧ Bits:30009717 Comet 32 harddisk image
    └─⟦28c352965⟧ »/a« UNIX Filesystem
        └─⟦this⟧ »usr/man/man2/killpg.2j« 

TextFile

.ig
	@(#)killpg.2j	2.1	7/1/84
	@(#)Copyright (C) 1983 by National Semiconductor Corp.
..
.TH KILLPG 2J
.UC 4
.SH NAME
killpg \- send signal to a process or a process group
.SH SYNOPSIS
.B killpg(pgrp, sig)
.PP
.B cc ... \-ljobs
.SH DESCRIPTION
.I Killpg
sends the signal
.I sig
to the specified process group.
See
.IR sigsys (2)
for a list of signals;
see
.IR jobs (3)
for an explanation of process groups.
.PP
The sending process and members of the process group must
have the same effective user ID, otherwise
this call is restricted to the super-user.
As a single special case the continue signal SIGCONT may be sent
to any process which is a descendant of the current process.  This
allows a command interpreter such as
.IR csh (1)
to restart set-user-id processes stopped from the keyboard with a stop signal.
.PP
The calls
.IP
.B "killpg(0, sig)"
.LP
and
.IP
.B "kill(0, sig)
.LP
have identical effects, sending the signal to all members of the
invoker's process group (including the process itself).
It is preferable to use the call involving
.I kill
in this case, as it is portable to other UNIX systems.
.SH "SEE ALSO"
jobs(3), kill(2), sigsys(2), signal(2), csh(1), kill(1)
.SH DIAGNOSTICS
Zero is returned if the processes are sent the signals;
\-1 is returned if any process in the process group cannot be sent
the signal, or if there are no members in the process group.
.SH BUGS
The job control facilities are not available in standard version 7 UNIX.
These facilities are still under development and may change in future
releases of the system as better inter-process communication facilities
and support for virtual terminals become available.  The options and
specifications of this system call and even the call itself
are thus subject to change.