GetWiki

{{Short description|Mechanism for inter-process communication using message passing}}{{About|the original implementation for shells|software pipelines in general|Pipeline (software)}}(File:Pipeline.svg|thumb|280px|A pipeline of three program processes run on a text terminal)In Unix-like computer operating systems, a pipeline is a mechanism for inter-process communication using message passing. A pipeline is a set of processes chained together by their standard streams, so that the output text of each process (stdout) is passed directly as input (stdin) to the next one. The second process is started as the first process is still executing, and they are executed concurrently. The concept of pipelines was championed by Douglas McIlroy at Unix’s ancestral home of Bell Labs, during the development of Unix, shaping its toolbox philosophy.WEB, Michael S., Mahoney,www.princeton.edu/~hos/Mahoney/expotape.htm, The Unix Oral History Project: Release.0, The Beginning, McIlroy: It was one of the only places where I very nearly exerted managerial control over Unix, was pushing for those things, yes., WEB,cm.bell-labs.com/cm/cs/who/dmr/mdmpipe.html, Prophetic Petroglyphs, cm.bell-labs.com, 22 May 2022,cm.bell-labs.com/cm/cs/who/dmr/mdmpipe.html," title="web.archive.org/web/19990508221104cm.bell-labs.com/cm/cs/who/dmr/mdmpipe.html,">web.archive.org/web/19990508221104cm.bell-labs.com/cm/cs/who/dmr/mdmpipe.html, 8 May 1999, dead, It is named by analogy to a physical pipeline. A key feature of these pipelines is their “hiding of internals� (Ritchie & Thompson, 1974). This in turn allows for more clarity and simplicity in the system.This article is about anonymous pipes, where data written by one process is buffered by the operating system until it is read by the next process, and this uni-directional channel disappears when the processes are completed. This differs from named pipes, where messages are passed to or from a pipe that is named by making it a file, and remains after the processes are completed. The standard shell syntax for anonymous pipes is to list multiple commands, separated by vertical bars (“pipes� in common Unix verbiage):command1 | command2 | command3For example, to list files in the current directory ({{mono|ls}}), retain only the lines of {{mono|ls}} output containing the string {{mono|“key“}} ({{mono|grep}}), and view the result in a scrolling page ({{mono|less}}), a user types the following into the command line of a terminal:ls -l | grep key | lessThe command ls -l is executed as a process, the output (stdout) of which is piped to the input (stdin) of the process for grep key; and likewise for the process for less. Each process takes input from the previous process and produces output for the next process via standard streams. Each | tells the shell to connect the standard output of the command on the left to the standard input of the command on the right by an inter-process communication mechanism called an (anonymous) pipe, implemented in the operating system. Pipes are unidirectional; data flows through the pipeline from left to right.

Example

Below is an example of a pipeline that implements a kind of spell checker for the web resource indicated by a URL. An explanation of what it does follows.curl â€en.Pseudopedia.org/wiki/Pipeline_(Unix)â€� |sed ‘s/[^a-zA-Z ]/ /g’ |tr ‘A-Z ‘ ‘a-zn’ |grep ‘[a-z]’ |sort -u |comm -23 -