jobs command in Linux CLI - Time & Space Complexity

Time Complexity: jobs command

O(n)

Understanding Time Complexity

We want to understand how the time to run the jobs command changes as the number of background tasks grows.

How does the command's work increase when there are more jobs to list?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

jobs

This command lists all current background jobs in the shell session.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The shell checks each background job to gather its status and details.
• How many times: Once for each job currently running or stopped in the background.

How Execution Grows With Input

As the number of background jobs increases, the command takes longer because it must check each job.

Input Size (n)	Approx. Operations
10	Checks 10 jobs
100	Checks 100 jobs
1000	Checks 1000 jobs

Pattern observation: The work grows directly with the number of jobs; doubling jobs doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to run jobs grows in a straight line with the number of background jobs.

Common Mistake

[X] Wrong: "The jobs command always runs instantly, no matter how many jobs there are."

[OK] Correct: The command must check each job, so more jobs mean more work and longer time.

Interview Connect

Understanding how commands scale with input size helps you think clearly about performance in real tasks.

Self-Check

"What if the shell cached job statuses instead of checking each time? How would the time complexity change?"

Practice

1. What does the jobs command do in a Linux shell?

easy

A. Lists background and stopped tasks in the current shell

B. Shows all running processes on the system

C. Terminates all background jobs

D. Starts a new background job

Solution

1. Step 1: Understand the purpose of jobs

   The jobs command shows tasks started in the current shell that are either stopped or running in the background.

2. Step 2: Compare with other options

   Options A, B, and C describe different commands or actions unrelated to jobs.

3. Final Answer:

   Lists background and stopped tasks in the current shell -> Option A

4. Quick Check:

   jobs lists current shell jobs [OK]

Hint: Remember: jobs shows your shell's paused or background tasks [OK]

Common Mistakes:

• Confusing jobs with ps command
• Thinking jobs starts or kills tasks
• Assuming jobs shows system-wide processes

2. Which of the following is the correct syntax to list all jobs with their process IDs using the jobs command?

easy

A. jobs -a

B. jobs --list-pid

C. jobs -p

D. jobs -l

Solution

1. Step 1: Recall jobs options

   The -l option with jobs lists jobs with their process IDs.

2. Step 2: Verify other options

   -p lists only PIDs without job info, --list-pid is invalid, and -a shows all jobs including those not started by the shell.

3. Final Answer:

   jobs -l -> Option D

4. Quick Check:

   jobs -l shows jobs with PIDs [OK]

Hint: Use -l to see job numbers plus process IDs [OK]

Common Mistakes:

• Using invalid options like --list-pid
• Confusing -p with -l
• Assuming -a shows PIDs

3. Given the following shell session:

$ sleep 100 &
[1] 12345
$ sleep 200 &
[2] 12346
$ jobs
[1]+  Running                 sleep 100 &
[2]-  Running                 sleep 200 &

What will be the output of jobs -l?

medium

A. [1]+ 12345 Stopped sleep 100 &
[2]- 12346 Stopped sleep 200 &

B. [1]+ Running sleep 100 &
[2]- Running sleep 200 &

C. [1]+ 12345 Running sleep 100 &
[2]- 12346 Running sleep 200 &

D. No jobs to display

Solution

1. Step 1: Understand jobs output

   The jobs command shows job number, status, and command. The -l option adds the process ID after the job number.

2. Step 2: Match output format

   Since both jobs are running with PIDs 12345 and 12346, jobs -l will show job number, PID, status, and command.

3. Final Answer:

   [1]+ 12345 Running sleep 100 & [2]- 12346 Running sleep 200 & -> Option C

4. Quick Check:

   jobs -l adds PIDs to normal jobs output [OK]

Hint: jobs -l shows PIDs next to job numbers [OK]

Common Mistakes:

• Ignoring PIDs in output
• Confusing Running with Stopped status
• Expecting no jobs listed

4. You ran sleep 300 & and then jobs shows the job as stopped. Which command will resume the job in the background?

medium

A. kill %1

B. bg %1

C. fg %1

D. stop %1

Solution

1. Step 1: Understand job states and commands

   A stopped job is paused. The bg command resumes it in the background, while fg resumes it in the foreground.

2. Step 2: Choose correct command for background resume

   Since the question asks to resume in background, bg %1 is correct. kill terminates, and stop is invalid here.

3. Final Answer:

   bg %1 -> Option B

4. Quick Check:

   Resume stopped job in background = bg %job_number [OK]

Hint: Use bg %job_number to resume stopped jobs in background [OK]

Common Mistakes:

• Using fg instead of bg for background resume
• Trying to kill instead of resume
• Using invalid stop command

5. You have multiple background jobs running. You want to bring job number 3 to the foreground and then stop it temporarily. Which sequence of commands should you use?

hard

A. fg %3, then press Ctrl+Z

B. bg %3, then press Ctrl+C

C. kill %3, then fg %3

D. jobs %3, then stop %3

Solution

1. Step 1: Bring job 3 to foreground

   Use fg %3 to bring job number 3 to the foreground so you can interact with it.

2. Step 2: Stop the job temporarily

   Pressing Ctrl+Z sends a stop signal, pausing the job and returning control to the shell.

3. Final Answer:

   fg %3, then press Ctrl+Z -> Option A

4. Quick Check:

   Foreground job then Ctrl+Z to stop it [OK]

Hint: Use fg %job then Ctrl+Z to pause foreground job [OK]

Common Mistakes:

• Using bg instead of fg to bring job forward
• Trying to kill instead of stop
• Using invalid stop command