How to Create Named Pipes for IPC Using the mkfifo Command in Linux

When you are architecting advanced inter-process communication (IPC) on a Linux server, passing massive amounts of data between two completely isolated scripts via standard temporary files is mathematically inefficient and causes catastrophic disk I/O bottlenecks. To mathematically force two separate terminal processes to communicate in real-time by streaming data directly through the system RAM, you must use the mkfifo command to construct a “named pipe.”

Constructing the IPC Architecture

Unlike a standard bash pipe (|) which only works between commands executed on the exact same line, a named pipe (FIFO – First In, First Out) acts like a physical file on your hard drive, but it stores zero actual data. It is merely a cryptographic gateway into the kernel’s memory buffer.

To execute the creation of a named pipe, type:

mkfifo /tmp/data_bridge

The exact millisecond you press Enter, the mkfifo engine constructs a special file in the /tmp directory. If you run ls -l /tmp/data_bridge, you will see a p at the absolute beginning of the permission string (e.g., prw-rw-r--), mathematically proving it is a pipe, not a standard file.

Executing the Real-Time Data Stream

Because the named pipe exists in the file system, two completely independent terminal windows can interact with it simultaneously.

1. Terminal 1 (The Receiver): Open a terminal window and instruct it to listen to the pipe by typing cat /tmp/data_bridge. The command will instantly hang. It is mathematically blocked, waiting for data to enter the pipeline.
2. Terminal 2 (The Sender): Open a completely separate terminal window and violently inject a string of data into the pipe by typing echo "CRITICAL SYSTEM ALERT" > /tmp/data_bridge.

The exact millisecond you press Enter in Terminal 2, the data is pushed into the RAM buffer. The kernel instantly routes it through the pipe, and it violently appears on the screen in Terminal 1. The data never touched the physical hard drive, completely bypassing standard disk latency and ensuring instantaneous inter-process synchronization.