Background processes (&) in Linux CLI - Commands & Configuration

Introduction

Sometimes you want to run a command but keep using the terminal for other tasks. Background processes let you do this by running commands without waiting for them to finish.

When you want to start a long download but still type other commands in the terminal.

When running a script that takes time and you want to continue working without waiting.

When launching a server or service and you want the terminal free for monitoring logs or other commands.

When testing commands that run continuously but you want to keep control of the terminal.

When automating tasks and you want multiple commands to run at the same time.

Commands

This command runs 'sleep 10' in the background, so the terminal is free immediately to run other commands.

Terminal

sleep 10 &

Expected Output

[1] 12345

Shows the list of background jobs currently running in this terminal session.

Terminal

jobs

Expected Output

[1]+  Running                 sleep 10

Brings the background job number 1 back to the foreground so you can interact with it or wait for it to finish.

Terminal

fg %1

Expected Output

sleep 10

Key Concept

If you remember nothing else from this pattern, remember: adding '&' after a command runs it in the background, freeing your terminal immediately.

Common Mistakes

Forgetting to add '&' at the end of the command.

The command runs in the foreground and blocks the terminal until it finishes.

Always add '&' at the end to run the command in the background.

Trying to bring a job to foreground with wrong job number.

The shell will show an error because the job number does not exist.

Use 'jobs' to check the correct job number before using 'fg %jobnumber'.

Closing the terminal without stopping background jobs.

Background jobs will be terminated when the terminal closes.

Use 'disown' or run jobs inside a terminal multiplexer if you want them to continue after closing.

Summary

Use '&' at the end of a command to run it in the background and free the terminal.

Use 'jobs' to see running background jobs and 'fg %jobnumber' to bring one back to the foreground.

Remember to manage background jobs properly to avoid losing work when closing the terminal.

Practice

1. What does adding & at the end of a command in Linux do?

easy

A. Runs the command with higher priority

B. Stops the command from running

C. Runs the command in the background, freeing the terminal immediately

D. Saves the command output to a file

Solution

1. Step 1: Understand the role of & in Linux commands

   Adding & at the end of a command tells the shell to run it in the background.

2. Step 2: Effect on terminal usability

   Running a command in the background frees the terminal immediately for other commands.

3. Final Answer:

   Runs the command in the background, freeing the terminal immediately -> Option C

4. Quick Check:

   Background process = command + & [OK]

Hint: Remember: & means run in background [OK]

Common Mistakes:

• Thinking & stops the command
• Confusing & with output redirection
• Assuming & increases priority

2. Which of the following is the correct syntax to run sleep 10 in the background?

easy

A. sleep & 10

B. & sleep 10

C. sleep 10 &&

D. sleep 10 &

Solution

1. Step 1: Identify correct placement of &

   The & must be at the end of the command to run it in the background.

2. Step 2: Check each option

   sleep 10 & places & correctly after sleep 10. Others place it incorrectly or use wrong syntax.

3. Final Answer:

   sleep 10 & -> Option D

4. Quick Check:

   Command + & at end = background run [OK]

Hint: Put & at the end of the command [OK]

Common Mistakes:

• Placing & before the command
• Using && instead of &
• Splitting & from command arguments

3. What will be the output after running these commands?

sleep 5 &
jobs

medium

A. Immediately exits the terminal

B. Lists the sleep job running in the background

C. Displays an error about sleep command

D. Shows no jobs running

Solution

1. Step 1: Run sleep 5 &

   This starts the sleep command in the background for 5 seconds.

2. Step 2: Run jobs

   This command lists all background jobs currently running, including the sleep job.

3. Final Answer:

   Lists the sleep job running in the background -> Option B

4. Quick Check:

   jobs shows background tasks [OK]

Hint: Use jobs to see background tasks [OK]

Common Mistakes:

• Expecting jobs to show nothing
• Confusing jobs with ps command
• Thinking sleep runs in foreground without &

4. You ran sleep 10 & but the job does not appear when you run jobs. What is the likely problem?

medium

A. You ran the command in a different shell session

B. The sleep command does not support background execution

C. You forgot to add & at the end

D. The jobs command is not installed

Solution

1. Step 1: Understand job control scope

   Background jobs are tracked per shell session. Running jobs in a different session won't show jobs from another.

2. Step 2: Check other options

   Sleep supports background execution, & was used, and jobs is a built-in command, so those are unlikely issues.

3. Final Answer:

   You ran the command in a different shell session -> Option A

4. Quick Check:

   jobs show current shell's background tasks only [OK]

Hint: jobs only shows current shell's background tasks [OK]

Common Mistakes:

• Assuming jobs shows all system background tasks
• Thinking sleep can't run in background
• Believing jobs is an external command

5. You want to run a script backup.sh in the background and bring it to the foreground later. Which sequence of commands is correct?

hard

A. ./backup.sh & fg %1

B. ./backup.sh && fg

C. ./backup.sh & jobs; fg %2

D. ./backup.sh & bg %1

Solution

1. Step 1: Run the script in background

   Use ./backup.sh & to start the script in the background.

2. Step 2: Bring the background job to foreground

   Use fg %1 to bring job number 1 (the backup script) to the foreground.

3. Step 3: Analyze options

   ./backup.sh & fg %1 correctly runs the script in background and then brings job 1 to foreground. ./backup.sh && fg uses logical && instead of &, so runs in foreground. ./backup.sh & jobs; fg %2 uses wrong job number %2. ./backup.sh & bg %1 uses bg which resumes background jobs, not foreground.

4. Final Answer:

   ./backup.sh & fg %1 -> Option A

5. Quick Check:

   Run with & then fg %job_number to foreground [OK]

Hint: Use fg %job_number to bring background job forward [OK]

Common Mistakes:

• Using && instead of & for background
• Using bg instead of fg to foreground
• Using wrong job number like %2