PDGETPID(2FREEBSD) - man page online | system calls
System calls to manage process descriptors.
August 28, 2013
PDFORK(2) BSD System Calls Manual PDFORK(2)
NAMEpdfork, pdgetpid, pdkill, pdwait4 — System calls to manage process descriptors
LIBRARYStandard C Library (libc, -lc)
SYNOPSIS#include <sys/procdesc.h> int pdfork(int *fdp, int flags); int pdgetpid(int fd, pid_t *pidp); int pdkill(int fd, int signum); int pdwait4(int fd, int *status, int options, struct rusage *rusage);
DESCRIPTIONProcess descriptors are special file descriptors that represent processes, and are created using pdfork(), a variant of fork(2), which, if successful, returns a process descriptor in the integer pointed to by fdp. Processes created via pdfork() will not cause SIGCHLD on termination. pdfork() can accept the flags: PD_DAEMON Instead of the default terminate-on-close behaviour, allow the process to live until it is explicitly killed with kill(2). This option is not permitted in capsicum(4) capability mode (see cap_enter(2)). pdgetpid() queries the process ID (PID) in the process descriptor fd. pdkill() is functionally identical to kill(2), except that it accepts a process descriptor, fd, rather than a PID. pdwait4() behaves identically to wait4(2), but operates with respect to a process descriptor argument rather than a PID. The following system calls also have effects specific to process descriptors: fstat(2) queries status of a process descriptor; currently only the st_mode, st_birthtime, st_atime, st_ctime and st_mtime fields are defined. If the owner read, write, and execute bits are set then the process represented by the process descriptor is still alive. poll(2) and select(2) allow waiting for process state transitions; currently only POLLHUP is defined, and will be raised when the process dies. close(2) will close the process descriptor unless PD_DAEMON is set; if the process is still alive and this is the last reference to the process descriptor, the process will be termi‐ nated with the signal SIGKILL. pdfork and associated functions depend on options PROCDESC described in procdesc(4).
RETURN VALUESpdfork() returns a PID, 0 or -1, as fork(2) does. pdgetpid() and pdkill() return 0 on success and -1 on failure. pdwait4() returns a PID on success and -1 on failure.
ERRORSThese functions may return the same error numbers as their PID-based equivalents (e.g. pdfork() may return the same error numbers as fork(2)), with the following additions: [EINVAL] The signal number given to pdkill() is invalid. [ENOTCAPABLE] The process descriptor being operated on has insufficient rights (e.g. CAP_PDKILL for pdkill()).
SEE ALSOclose(2), fork(2), fstat(2), kill(2), poll(2), wait4(2), capsicum(4), procdesc(4)
HISTORYThe pdfork(), pdgetpid(), pdkill() and pdwait4() system calls first appeared in FreeBSD 9.0. Support for process descriptors mode was developed as part of the TrustedBSD Project.
AUTHORSThese functions and the capability facility were created by Robert N. M. Watson <@FreeBSD.org> and Jonathan Anderson <@FreeBSD.org> at the University of Cam‐ bridge Computer Laboratory with support from a grant from Google, Inc.
BSD August 28, 2013 BSD
BUGSpdwait4() has not yet been implemented.
|This manual||Reference||Other manuals|
|pdgetpid(2freebsd)||referred by||capsicum(4freebsd) | procdesc(4freebsd) | rights(4freebsd)|
|refer to||cap_enter(2freebsd) | capsicum(4freebsd) | close(2) | fork(2) | kill(2) | pdfork(2freebsd) | poll(2) | procdesc(4freebsd) | select(2) | stat(2) | wait4(2)|