[Solved] You run sleep 100 & but jobs shows no output. What is the likely cause? — Ans: The job was started in a different shell session | Linux CLI

Linux CLI - Process Management

You run sleep 100 & but jobs shows no output. What is the likely cause?

AThe sleep command failed to start

BThe job was started in a different shell session

Cjobs command is broken

DThe job finished instantly

Step-by-Step Solution

Solution:

Step 1: Understand jobs scope
jobs only shows jobs started in the current shell session.
Step 2: Analyze possible causes
If job was started elsewhere, current shell's jobs list is empty; sleep usually doesn't fail silently or finish instantly.
Final Answer:
The job was started in a different shell session -> Option B
Quick Check:
jobs shows current shell jobs only [OK]

Quick Trick: jobs only lists jobs from current shell session [OK]

Common Mistakes:

Master "Process Management" in Linux CLI

9 interactive learning modes - each teaches the same concept differently

More Linux CLI Quizzes

You run sleep 100 & but jobs shows no output. What is the likely cause?