Explore >> Select a destination
|
You are here 
|
blog.rubenwardy.com | ||
| | | | |
blog.nelhage.com
|
|
| | | | | (This is part three of a multi-part introduction to termios and terminal emulation on UNIX. Read part 1 or part 2 if you're new here) For my final entry on termios, I will be looking at job control in the shell (i.e. backgrounding and foreground jobs) and the very closely related topic of signal generation by termios, in response to INTR and friends. Sessions and Process Groups For the purposes of termios, processes are organized into two hierarchical groups, process groups and sessions. | |
| | | | |
ariadne.space
|
|
| | | | | A historical defect in the ifupdown suite has been the lack of proper supervision of processes run by the system in order to bring up and down interfaces. Specifically, it is possible in historical ifupdown for a process to hang forever, at which point the system will fail to finish configuring interfaces. | |
| | | | |
blog.eldruin.com
|
|
| | | | | Example of inter-process comunication in C++ using STL-like streams. | |
| | | | |
opensourcemusings.com
|
|
| | | |||
