Pipe operator (|) in Linux CLI - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the pipe operator (|) do in Linux command line?

It takes the output of one command and uses it as the input for the next command, allowing commands to be chained together.

beginner

How would you explain the pipe operator using a real-life example?

Imagine a factory assembly line where one worker passes a part to the next worker. The pipe operator is like passing the output from one command (worker) directly to the next for further processing.

beginner

Which command uses the pipe operator to count the number of lines in a file named 'notes.txt'?

cat notes.txt | wc -l Here, 'cat notes.txt' outputs the file content, and 'wc -l' counts the lines from that output.

beginner

True or False: The pipe operator can only connect two commands.

False. You can chain multiple commands with several pipe operators, passing output through a series of commands.

intermediate

What happens if you use the pipe operator with a command that produces no output?

The next command in the pipe receives no input and may produce no output or behave differently depending on the command.

What is the main purpose of the pipe operator (|) in Linux?

A To comment out a command

B To run two commands at the same time

C To send output of one command as input to another

D To save command output to a file

The pipe operator connects commands by passing output from one as input to the next.

Which command uses the pipe operator correctly?

A ls & grep txt

B ls > grep txt

C ls ; grep txt

D ls | grep txt

'ls | grep txt' sends the list of files to grep to filter those containing 'txt'.

If you want to count how many files have '.log' in their name, which command uses pipe correctly?

A ls > grep .log > wc -l

B ls | grep .log | wc -l

C ls & grep .log & wc -l

D ls ; grep .log ; wc -l

The pipe chains commands: list files, filter '.log', then count lines.

What will happen if the first command in a pipe produces no output?

A The next command receives no input and may produce no output

B The next command runs normally with default input

C The pipe operator will cause an error

D The first command will restart automatically

No output means no input for the next command, so it may produce no output.

Can you use multiple pipes in one command line?

A Yes, to chain several commands

B No, only one pipe is allowed

C Yes, but only two pipes max

D No, pipes are deprecated

Multiple pipes can chain many commands together in sequence.

Explain how the pipe operator (|) works in Linux command line and give a simple example.

Think about how you can connect commands to work together.

Describe a real-life analogy that helps understand the pipe operator in Linux.

Imagine how things move from one person to another in a process.

Practice

1. What does the pipe operator | do in Linux command line?

easy

A. Sends the output of one command as input to another command

B. Runs two commands simultaneously

C. Redirects output to a file

D. Comments out a line in a script

Solution

1. Step 1: Understand the pipe operator function

   The pipe operator | takes the output from the command on its left side.

2. Step 2: Connect output to input of next command

   This output is then passed as input to the command on the right side of the pipe.

3. Final Answer:

   Sends the output of one command as input to another command -> Option A

4. Quick Check:

   Pipe operator = send output to next command [OK]

Hint: Pipe connects output to input of next command [OK]

Common Mistakes:

• Thinking pipe runs commands in parallel
• Confusing pipe with output redirection >
• Assuming pipe comments code lines

2. Which of the following is the correct syntax to use the pipe operator to list files and then count them?

easy

A. ls & wc -l

B. ls > wc -l

C. ls || wc -l

D. ls | wc -l

Solution

1. Step 1: Identify correct pipe syntax

   The pipe operator is |, which connects commands by passing output to input.

2. Step 2: Check command usage

   ls | wc -l lists files and counts lines, which is correct syntax.

3. Final Answer:

   ls | wc -l -> Option D

4. Quick Check:

   Pipe syntax uses | between commands [OK]

Hint: Use single | to pipe commands, not > or & [OK]

Common Mistakes:

• Using > which redirects output to file
• Using & which runs commands in background
• Using || which is logical OR, not pipe

3. What is the output of the command: echo -e "apple\nbanana\ncherry" | grep "an"?

medium

A. apple cherry

B. apple banana cherry

C. banana

D. No output

Solution

1. Step 1: Understand the echo command output

   echo -e "apple\nbanana\ncherry" outputs three lines: apple, banana, cherry.

2. Step 2: Apply grep filter with "an"

   grep "an" filters lines containing "an", which matches only "banana".

3. Final Answer:

   banana -> Option C

4. Quick Check:

   grep filters lines with 'an' = banana [OK]

Hint: grep filters lines containing the pattern [OK]

Common Mistakes:

• Expecting all words printed on one line
• Ignoring newline characters in echo
• Thinking grep matches partial words only

4. Identify the error in this command: cat file.txt | | grep "error"

medium

A. No error, command runs fine

B. Extra pipe operator causes syntax error

C. grep command is misspelled

D. Missing filename after cat

Solution

1. Step 1: Analyze the pipe usage

   The command has two pipe operators | | consecutively, which is invalid syntax.

2. Step 2: Understand correct pipe usage

   Only one pipe operator should separate commands; extra pipes cause errors.

3. Final Answer:

   Extra pipe operator causes syntax error -> Option B

4. Quick Check:

   Double pipes cause syntax error [OK]

Hint: Use single | between commands, no doubles [OK]

Common Mistakes:

• Ignoring extra pipe and expecting output
• Thinking missing filename is the error
• Assuming grep is misspelled

5. You want to find how many lines in log.txt contain the word "fail" but ignore case. Which command correctly uses pipes to do this?

hard

A. cat log.txt | grep -i fail | wc -l

B. grep fail log.txt | wc -l

C. cat log.txt > grep -i fail | wc -l

D. grep -i fail | cat log.txt | wc -l

Solution

1. Step 1: Use cat to output file content

   cat log.txt outputs the file content to pipe.

2. Step 2: Use grep with -i to ignore case

   grep -i fail filters lines containing "fail" ignoring case.

3. Step 3: Count lines with wc -l

   wc -l counts the filtered lines.

4. Final Answer:

   cat log.txt | grep -i fail | wc -l -> Option A

5. Quick Check:

   Pipe commands to filter and count lines [OK]

Hint: Pipe cat to grep -i then to wc -l for case-insensitive count [OK]

Common Mistakes:

• Using > instead of | breaks pipe chain
• Placing commands in wrong order
• Omitting -i for case-insensitive search