Repository files navigation

"This project is about handling pipes..."

You may need some knowledge aboutthis art and the pipex project to understand this banner... 🙃

• Introduction
• First things first
• Usage
• Explanation
• Bonus
• Bonus Usage
• Makefile Overview
• License

Pipex is a project about file descriptors redirections, process management, executing commands and pipes. 😊
This project presents some new concepts that we havent seen until now: processes, file descriptor redirection and pipes.To understand better what are the requirements of this project, see thesubject.

This project's code was written according to the42 norm guidelines(norminette).

First of all, I would like to thank the people who gave time and energy to construct incredible articles and videos about file descriptors redirection, forks, pipes, executions, processes, and C programming in general. Thank you very much!Here are some of the sources that I used to understand the concepts behind everything in this project:

• Pipe: An Inter-Process Communication Method ByMia Combeau.
• Youtube playlist by CodeVault ByCode Vault.
• Pipes, Forks, and Dups ByRoslyn Michelle Cyrus McConnell
• Pipex Tutorial: 42 Project Byzihan
• A Comprehensive Guide to Pipex Byherbievine

Thank you very much for the contribution to the community.

To use the pipex project, follow these steps:

1. Clone the repository

git clone git@github.com:amauricoder/42_Pipex.git

2. Do make to compile the files

make

This will generate the pipex file in the root folder, that is executable of the program.

3. Create an infile and write some information inside.

touch infilevim infile

You can also create a simple .txt file with text inside.

4. execute the program with the following paramethers

./pipex infile"cmd1""cmd2" outfile

Where

• infile: This refers to the input file used within the project.
• cmd1: This denotes the first command, which will have its output redirected from the infile to the pipe.
• cmd2: This represents the second command, which will have its input redirected from the pipe and its output sent to the outfile.
• outfile: This is the file designated to receive the output of the commands.Examples:

- ./pipex infile"ls -l -a -h -G -r -R""wc -l" outfile

- ./pipex infile"sed s/a/A/g""wc -c" outfile

- ./pipex infile"tail -n 5""grep pattern" outfile

Important!
To understand how this project works, we need to understand some important concepts. I will explain some of these concepts in a very concise way below. I do recommend for you to read the articles and watch the videos above for a better and deeper understanding.

• Processes: Are instances of a program. They have their own memory scope. A program can have multiple processes running in parallel at the same time.
• Pipes: Pipes are spaces in memory that allow two processes to communicate with each other in an efficient way. They have file descriptors to read information and to write.
• File Descriptors: Are numbers used by a computer to identify open files. They're like labels for files, allowing programs to read from and write to them. For example, stdin (0), stdout (1), and stderr (2) are standard descriptors for input, output, and error streams, respectively.
• STDIN_FILENO and STDOUT_FILENO: Are macros for the standard read and write file descriptors from the terminal. They are defined in <unistd.h>.

This project basically creates a process for the first command. For this specific process, it redirects the STDIN_FILENO to the infile and STDOUT_FILENO to the write side of the pipe, through the dup2() function. And then, it executes the command. When the command is executed, the process ends. This means that for the first command, it will read information from the input file, and after executing, the output will be sent to the pipe.For the second command, the process that will be responsible is the parent process. It redirects the STDOUT_FILENO to the outfile, and the STDIN_FILENO to the read side of the pipe. And then, it executes the command. This means that for the second command, it will read the information that is inside the pipe, execute the command with this information, and will redirect the information to the outfile.

For the bonus part, we needed to reproduce the behaviour of here_doc and the behaviour of a pipeline. A pipeline in a very simple and not deep explanation is having a pipe redirecting information to another one. For more informations about this part of the project, see thesubject.The bonus part is a little more complicated than the main project.Basically, we need to check if we have here_doc, if we have we will receive the information and here_doc will replace the infile. Then, we needed to create a process for every command(except for the last, that will be treated for the main process).The logic of redirection is basically the same as in the main project, but here we will redirect from one pipe to another inside the loop.

To use the pipex bonus, follow these steps:Considering you already have cloned your repository:

1. Do make to compile the files

make bonus

considering you already have an infile:2. execute the program with the following paramethers

./pipex_bonus infile"cmd1""cmd2""cmd3" ...."cmdN" outfile

or

./pipex_bonus here_doc LIMITER"cmd1""cmd2""cmd3" ...."cmdN" outfile

Examples:

- ./pipex_bonus infile"sed s/a/A/g""grep 'pattern'""wc -c" outfile

- ./pipex_bonus here_doc LIMITER"tail -n 5""grep pattern" outfile

Where

• infile: This refers to the input file used within the project.
• cmd1: This denotes the first command, which will have its output redirected from the infile to the pipe.
• cmd... : These are the commads of the middle. Theu will have this input and output redirected from pipe to pipe.
• cmdN: This represents the last command, which will have its input redirected from the pipe and its output sent to the outfile.
• outfile: This is the file designated to receive the output of the commands.Examples:

- ./pipex infile"ls -l -a -h -G -r -R""wc -l" outfile

- ./pipex infile"sed s/a/A/g""wc -c" outfile

- ./pipex infile"tail -n 5""grep pattern" outfile

In this project, the Makefile offers the following essential rules:

• make: Compiles the main project topipex executable.

• make clean: Cleans the directory by removing.o files, preservingpipex executable.

• make fclean: Completely cleans the directory by deleting both.o files andpipex executable.

• make re: Refreshespipex by recompiling everything.

Additionally:

• make bonus: Compiles the bonus project topipex_bonus executable.
• make bre: Refreshes thepipex_bonus by recompiling everything.

View License

You are free to use this project as you want.However, I don't recommend copying it if you don't understand the concepts involved and are unable to reconstruct it from scratch. Good luck!