2.12.2018
Implementation of redirection and pipe operators in shell — Sarath Lakshman
http://www.sarathlakshman.com/2012/09/24/implementation-overview-of-redirection-and-pipe-operators-in-shell?fbclid=IwAR3…
1/5
SEPTEMBER 24, 2012
Implementation of redirection and
pipe operators in shell
I have been always fascinated about the design of UNIX. I am still
curious and enjoy the philosophy and the idea of ‘Write programs
that do one thing and do it well’. Aim of this blog post is to walk
through some interesting aspects on implementation of le
descriptors and to illustrate how gracefully that design helps to build
interesting unix shell methodologies. For any process, there are three
default le descriptors. Stdin - with descriptor number 0, Stdout -
with descriptor number 1 and Stderr with descriptor number 2.
Let us go through some basic system calls. All the system calls
explained below are not exact syntax. Please refer man for correct
function prototype.
1. fork()
The fork system call creates another copy of current process and
mark the new process as child of parent process which called fork.
This system call returns zero in the child process and return child’s
pid in the parent process. It copies everything including le
descriptors, and virtual memory. If a process tries to write any virtual
memory page, it will do a copy on write to create copy of that
particular page for that process space.
2. exec(binary_path)
The exec system call overwrites the current process with executable
image from a le. Eg. if you run exec(“/bin/ls”). It will overwrite the
memory code image with binary from /bin/ls and execute. The le
descriptor table remains the same as that of original process.
3. open( le, mode)
HOME (/)
CODE (http://github.com/t3rm1n4l)
PUBLICATIONS (/publications)
TALKS (/talks)
ABOUT (/about)
2.12.2018
Implementation of redirection and pipe operators in shell — Sarath Lakshman
http://www.sarathlakshman.com/2012/09/24/implementation-overview-of-redirection-and-pipe-operators-in-shell?fbclid=IwAR3…
2/5
Opens a le and creates a le descriptor associated with the le.
IMPORTANT: By design, when the kernel allocates a le descriptor, it
will create the fd with next smallest available le descriptor number.
4. close(fd)
Closes the open le descriptor
5. dup(fd)
The dup system call creates a le descriptor that is duplicate of given
fd passed as argument.
6. pipe(int arr[2])
Creates a pipe, and stores the read descriptor in array location zero
and write descriptor in array location one.
7. read(fd, bu , len)
Reads len bytes to bu from le descriptor fd.
8. write(fd, bu , len)
Writes len bytes from bu to le descriptor fd.
Let us go through some interesting shell features that we use
frequently and look at their implementations.
Redirections
$ cmd1 > stdout.txt
The above command redirects stdout to le stdout.txt
For implementing the above operation, we should be able to link
stdout of cmd1 with le descriptor of stdout.txt opened with write
mode. Let us look at the code.
2.12.2018
Implementation of redirection and pipe operators in shell — Sarath Lakshman
http://www.sarathlakshman.com/2012/09/24/implementation-overview-of-redirection-and-pipe-operators-in-shell?fbclid=IwAR3…
3/5
1
2
3
4
5
6
7
8
9
main(){
close(1); // Release fd no - 1
open("stdout.txt", "w"); // Open a file with fd no = 1
// Child process
if (fork() == 0) {
exec("cmd1"); // By default, the program writes to stdout (fd no - 1).
ie, in this case, the file
}
}
$ cmd1 2> stdout.txt
The above command redirects stderr to le stdout.txt
1
2
3
4
5
6
7
8
main(){
close(2); // Release fd no - 2
open("stderr.txt", "w"); // Opens file with fd no - 2
// Child process
if (fork() == 0) {
exec("cmd1"); // Writes to stderr (fd no 2)
}
}
$ cmd2 > stdout_stderr.txt 2>&1
The above command redirects both stdout and stderr to le
stdout_stderr.txt
1
2
3
4
5
6
7
8
9
1
0
main(){
close(1); // Release fd no - 1
open("stdout_stderr.txt", "w"); //Opens file with fd no - 1
// Child process
if (fork() == 0) {
close(2); // Release fd no - 2
dup(1); // Create fd no - 2 which is duplicate of fd no -1. Hence, we j
oined fd 1 and 2 (stdout and stderr)
exec("cmd2");
}
}
$ cmd3 < input.txt
The above command redirects data from input.txt to stdin for cmd3.
2.12.2018
Implementation of redirection and pipe operators in shell — Sarath Lakshman
http://www.sarathlakshman.com/2012/09/24/implementation-overview-of-redirection-and-pipe-operators-in-shell?fbclid=IwAR3…
4/5
1
2
3
4
5
6
7
8
9
main(){
close(0);//Release fd - 0
open("stdout.txt", "r"); //Open file with fd - 0
//Child process
if (fork() == 0) {
exec("cmd3"); // By default, program reads from stdin. ie, fd - 0
}
}
Pipe
$ cmd1 | cmd2
This command says that cmd2 will receive stdin from stdout of cmd1.
1
2
3
4
5
6
7
8
9
1
0
1
1
1
2
1
3
1
4
1
5
1
6
1
7
1
8
1
9
2
0
main(){
int p[2];
pipe(p); // Creates a pipe with file descriptors Eg. input = 3 and output =
4 (Since, 0,1 and 2 are not available)
if (fork() == 0) {
// Child process
close(0); // Release fd no - 0
close(p[0]); // Close pipe fds since useful one is duplicated
close(p[1]);
dup(p[0]); // Create duplicate of fd - 3 (pipe read end) with fd 0.
exec("cmd2");
} else {
//Parent process
close(1); // Release fd no - 1
close(p[0]); // Close pipe fds since useful one is duplicated
close(p[1]);
dup(p[1]); // Create duplicate of fd - 4 (pipe write end) with fd 1.
exec("cmd1");
}
}
Aren’t you feeling awesome? With simple design, without making any
code change to individual programs, it is possible to connect input
and output streams to individual programs. Hats o to designers of
UNIX.
Tweet
submit
Like 0
