Bird
0
0

Why does the jobs command not show jobs started with nohup?

hard📝 Conceptual Q10 of 15
Linux CLI - Process Management
Why does the jobs command not show jobs started with nohup?
ABecause nohup disables background execution
BBecause nohup jobs run too fast to appear
CBecause jobs only shows root user's jobs
DBecause nohup detaches the job from the shell's job control
Step-by-Step Solution
Solution:

  1. Step 1: Understand nohup behavior

    nohup detaches a process from the shell, ignoring hangup signals and removing it from job control.

  2. Step 2: Analyze jobs command scope

    jobs only shows jobs under shell's job control, so nohup jobs are not listed.

  3. Final Answer:

    Because nohup detaches the job from the shell's job control -> Option D

  4. Quick Check:

    nohup detaches jobs from shell control [OK]
Quick Trick: nohup detaches jobs from shell control, so jobs won't list them [OK]
Common Mistakes:
  • Thinking jobs shows all system jobs
  • Assuming nohup disables background
  • Believing jobs shows only root jobs

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Linux CLI Quizzes
Disk and Storage - df (disk free space) - Quiz 1easy Networking Commands - wget for file downloads - Quiz 7medium Networking Commands - ping for connectivity testing - Quiz 15hard Pipes and Redirection - Command chaining (&&, ||, ;) - Quiz 8hard Pipes and Redirection - Pipe operator (|) - Quiz 14medium Pipes and Redirection - /dev/null for discarding output - Quiz 10hard Process Management - kill and signal types - Quiz 4medium Searching and Finding - find with -exec for actions - Quiz 2easy Searching and Finding - which and whereis for commands - Quiz 9hard Searching and Finding - find by modification time - Quiz 5medium