Bird
0
0

You run kill -9 4321 but the process with PID 4321 does not terminate. What is the most likely reason?

medium📝 Debug Q6 of 15
Linux CLI - Process Management
You run kill -9 4321 but the process with PID 4321 does not terminate. What is the most likely reason?
AThe process is ignoring SIGKILL
BYou do not have permission to kill the process
CSIGKILL cannot terminate processes
DThe PID 4321 does not exist
Step-by-Step Solution
Solution:

  1. Step 1: Understand SIGKILL behavior

    SIGKILL (signal 9) cannot be ignored and always terminates a process if allowed.

  2. Step 2: Check permissions and PID existence

    If process does not terminate, likely you lack permission or PID does not exist.

  3. Step 3: Differentiate reasons

    If PID existed, permission issue is most common cause.

  4. Final Answer:

    You do not have permission to kill the process -> Option B

  5. Quick Check:

    SIGKILL always kills if permitted [OK]
Quick Trick: SIGKILL can't be ignored; check permissions [OK]
Common Mistakes:
  • Thinking SIGKILL can be ignored
  • Assuming PID always exists
  • Believing SIGKILL doesn't terminate

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Linux CLI Quizzes
Disk and Storage - Why disk management prevents outages - Quiz 8hard Disk and Storage - du (disk usage by directory) - Quiz 1easy Networking Commands - nslookup and dig for DNS - Quiz 8hard Networking Commands - scp and rsync for file transfer - Quiz 3easy Networking Commands - curl for HTTP requests - Quiz 9hard Pipes and Redirection - Command chaining (&&, ||, ;) - Quiz 5medium Pipes and Redirection - Command chaining (&&, ||, ;) - Quiz 1easy Process Management - nohup for persistent processes - Quiz 2easy Searching and Finding - find by modification time - Quiz 11easy Text Processing - awk patterns and actions - Quiz 7medium