✳flâneur — a map of the web's best reading

tldp.org/LDP/tlk/ipc/ipc.html

tldp.org · 4,329 words · saved by 1 readers

Processes communicate with each other and with the kernel to coordinate their activities. Linux supports a number of Inter-Process Communication (IPC) mechanisms. Signals and pipes are two of them but Linux also supports the System V IPC mechanisms named after the Unix TM release in which they first appeared. There are a set of defined signals that the kernel can generate or that can be generated by other processes in the system, provided that they have the correct privileges. You can list a system's set of signals using the kill command (kill -l), on my Intel Linux box this gives: The numbers are different for an Alpha AXP Linux box. Processes can choose to ignore most of the signals that are generated, with two notable exceptions: neither the SIGSTOP signal which causes a process to halt its execution nor the SIGKILL signal which causes a process to exit can be ignored. Otherwise though, a process can choose just how it wants to handle the various signals. Processes can block the sig

Table of Contents , Show Frames , No Frames Chapter 5 Interprocess Communication Mechanisms Processes communicate with each other and with the kernel to coordinate their activities. Linux supports a number of Inter-Process Communication (IPC) mechanisms. Signals and pipes are two of them but Linux also supports the System V IPC mechanisms named after the Unix T M release in which they first appeared. 5.1 Signals Signals are one of the oldest inter-process communication methods used by Unix T M systems. They are used to signal asynchronous events to one or more processes. A signal could be gene

Explore this link on the map →

related reading