Command chaining (&&, ||, ;) in Linux CLI - Commands & Configuration

Introduction

Sometimes you want to run several commands one after another in the terminal. Command chaining lets you connect commands so they run in order, depending on whether the previous command worked or not. This helps you automate tasks without typing each command separately.

When you want to run a backup command only if the previous command to prepare files succeeded.

When you want to try a command and if it fails, run a different command to fix the problem.

When you want to run multiple commands one after another regardless of success or failure.

When you want to save time by running several commands in one line instead of typing them separately.

Commands

This command creates a directory named 'test_dir'. If the directory is created successfully, it prints 'Directory created'. The '&&' means the second command runs only if the first succeeds.

Terminal

mkdir test_dir && echo "Directory created"

Expected Output

Directory created

This tries to create 'test_dir'. If it fails (for example, if the directory already exists), it prints 'Failed to create directory'. The '||' means the second command runs only if the first fails.

Terminal

mkdir test_dir || echo "Failed to create directory"

Expected Output

mkdir: cannot create directory 'test_dir': File exists

Failed to create directory

This runs two commands one after another no matter what. The ';' separates commands and both run regardless of success or failure.

Terminal

echo "First command"; echo "Second command"

Expected Output

First command

Second command

Key Concept

If you remember nothing else from this pattern, remember: '&&' runs the next command only if the first succeeds, '||' runs the next command only if the first fails, and ';' runs commands one after another no matter what.

Common Mistakes

Using '&&' when you want the second command to run regardless of the first command's success.

The second command will not run if the first command fails, which may stop your script unexpectedly.

Use ';' to run commands sequentially regardless of success or failure.

Using '||' expecting the second command to run only if the first command succeeds.

'||' runs the second command only if the first command fails, so it behaves opposite to what is expected.

Use '&&' if you want the second command to run only on success.

Not quoting strings with spaces in chained commands.

The shell may split the string into multiple arguments causing errors.

Always quote strings with spaces, like echo "Directory created".

Summary

Use '&&' to run the next command only if the previous command succeeds.

Use '||' to run the next command only if the previous command fails.

Use ';' to run commands one after another regardless of success or failure.

Practice

1. What does the command chaining operator && do in Linux shell?

easy

A. Runs the next command only if the previous command succeeded

B. Runs the next command only if the previous command failed

C. Runs all commands regardless of previous command success

D. Runs the next command in the background

Solution

1. Step 1: Understand the meaning of &&

   The && operator runs the next command only if the previous command returns success (exit status 0).

2. Step 2: Compare with other operators

   || runs next command only if previous failed, and ; runs commands regardless of success.

3. Final Answer:

   Runs the next command only if the previous command succeeded -> Option A

4. Quick Check:

   && means run next if success [OK]

Hint: Remember: && means next runs only on success [OK]

Common Mistakes:

• Confusing && with ||
• Thinking && runs commands regardless
• Assuming && runs commands in background

2. Which of the following is the correct syntax to run cmd1 and then cmd2 regardless of cmd1's success or failure?

easy

A. cmd1 && cmd2

B. cmd1 || cmd2

C. cmd1 ; cmd2

D. cmd1 & cmd2

Solution

1. Step 1: Identify the operator that runs commands regardless

   The semicolon ; runs commands one after another no matter if the first succeeds or fails.

2. Step 2: Check other options

   && runs next only if first succeeds, || runs next only if first fails, & runs command in background.

3. Final Answer:

   cmd1 ; cmd2 -> Option C

4. Quick Check:

   ; runs commands regardless [OK]

Hint: Use ; to run commands one after another always [OK]

Common Mistakes:

• Using && or || when unconditional run is needed
• Confusing & (background) with ;
• Missing spaces around operators

3. What will be the output of the following commands if file.txt does not exist?
cat file.txt && echo "File exists" || echo "File missing"

medium

A. File exists

B. File missing

C. No output

D. cat: file.txt: No such file or directory

Solution

1. Step 1: Understand command chaining behavior

   cat file.txt fails because file does not exist, so && echo "File exists" is skipped, and || echo "File missing" runs.

2. Step 2: Predict output

   The error message from cat is printed to stderr (not shown here), but the command output from chaining is File missing.

3. Final Answer:

   File missing -> Option B

4. Quick Check:

   Failed cat triggers || echo [OK]

Hint: Remember: || runs next if previous fails [OK]

Common Mistakes:

• Expecting 'File exists' output
• Ignoring that cat prints error to stderr
• Thinking no output appears

4. Identify the error in this command chaining:
mkdir newdir || echo "Created" && cd newdir

medium

A. The echo message is incorrect

B. mkdir should be followed by ; not ||

C. The chaining logic runs cd only if echo runs

D. No error, command works as intended

Solution

1. Step 1: Analyze the chaining logic

   Operators || and && have equal precedence and associate left-to-right: parsed as (mkdir newdir || echo "Created") && cd newdir.

2. Step 2: Trace execution

   mkdir success: skip echo, success && cd runs. mkdir fail: run echo "Created" (success) && cd runs. Error: echo "Created" runs only on failure (dir exists), wrong message.

3. Final Answer:

   The echo message is incorrect -> Option A

4. Quick Check:

   || echo "Created" runs on mkdir fail [OK]

Hint: || triggers echo only on failure, check message [OK]

Common Mistakes:

• Misparsing as right-associative (mkdir || (echo && cd))
• Thinking cd skips on mkdir success
• Overlooking echo on mkdir failure

5. You want to run backup.sh only if prepare.sh succeeds, but if prepare.sh fails, you want to run cleanup.sh. Which command chaining achieves this?

hard

A. prepare.sh || cleanup.sh && backup.sh

B. prepare.sh && (backup.sh || cleanup.sh)

C. prepare.sh ; backup.sh ; cleanup.sh

D. prepare.sh && backup.sh || cleanup.sh

Solution

1. Step 1: Understand the requirement

   Run backup.sh only if prepare.sh succeeds; if prepare.sh fails, run cleanup.sh.

2. Step 2: Analyze prepare.sh && backup.sh || cleanup.sh

   prepare.sh && backup.sh || cleanup.sh means: if prepare.sh succeeds, run backup.sh. If either prepare.sh or backup.sh fails, run cleanup.sh. This matches the requirement.

3. Final Answer:

   prepare.sh && backup.sh || cleanup.sh -> Option D

4. Quick Check:

   Run backup if prepare succeeds, else cleanup [OK]

Hint: Use && then || to handle success and failure paths [OK]

Common Mistakes:

• Running cleanup even if prepare succeeds
• Running backup even if prepare fails
• Using ; which ignores success/failure