Why process control manages running programs in Linux CLI - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Process Control in Linux

Why does process control exist to manage running programs in Linux?

A To increase the size of files on the disk automatically

B To allow the system to start, stop, and monitor programs efficiently

C To change the color scheme of the terminal interface

D To permanently delete all user data without confirmation

💡 Hint

Think about what managing running programs means in terms of system resources.

Process control helps the operating system handle programs by starting, stopping, and keeping track of them so the system runs smoothly.

💻 Command Output

intermediate

Output of 'ps' Command

What is the output of the command ps -e | grep bash on a Linux system?

Linux CLI

ps -e | grep bash

A Lists all running processes including those with 'bash' in their name

B Shows the disk usage of the bash shell

C Displays the contents of the bash configuration file

D Deletes all bash processes immediately

💡 Hint

The 'ps' command lists processes; 'grep' filters output.

The command lists all running processes and filters to show only those with 'bash' in their name, showing active bash shells.

📝 Syntax

advanced

Correct Syntax to Kill a Process

Which command correctly stops a running process with PID 1234?

A kill 1234 -k

B kill 1234 -9

C kill -9 1234

D kill -x 1234

💡 Hint

The signal option comes immediately after 'kill'.

The correct syntax is 'kill -9 1234' where '-9' is the signal to force kill the process with PID 1234.

🔧 Debug

advanced

Why Does 'kill 1234 -9' Fail?

Given the command kill 1234 -9, why does it fail to stop the process?

A Because 'kill' cannot stop processes

B Because PID 1234 does not exist

C Because '-9' is not a valid signal

D Because the signal option '-9' must come before the PID

💡 Hint

Check the order of arguments in the kill command.

The kill command expects the signal option before the PID. Writing 'kill 1234 -9' treats '-9' as a PID, causing failure.

🚀 Application

expert

Using 'top' to Identify High CPU Processes

You want to find which running program is using the most CPU on your Linux system. Which steps using the 'top' command will help you do this?

A Run 'top', then press 'P' to sort processes by CPU usage descending

B Run 'top', then press 'M' to sort processes by memory usage ascending

C Run 'top', then press 'T' to sort processes by time ascending

D Run 'top', then press 'Q' to quit immediately

💡 Hint

Look for the key that sorts by CPU usage in descending order.

Pressing 'P' in 'top' sorts the process list by CPU usage from highest to lowest, helping identify the most CPU-intensive programs.

Practice

1. What is the main purpose of process control in Linux?

easy

A. To manage running programs by starting, stopping, or pausing them

B. To install new software packages

C. To change the screen resolution

D. To create new user accounts

Solution

1. Step 1: Understand process control basics

   Process control is about managing programs that are currently running on the system.

2. Step 2: Identify the correct purpose

   Starting, stopping, and pausing programs are key actions in process control.

3. Final Answer:

   To manage running programs by starting, stopping, or pausing them -> Option A

4. Quick Check:

   Process control = Manage running programs [OK]

Hint: Process control means managing running programs [OK]

Common Mistakes:

• Confusing process control with software installation
• Thinking it manages hardware settings
• Mixing it up with user account management

2. Which command is used to pause a running process in Linux?

easy

A. kill -9 <pid>

B. kill -STOP <pid>

C. kill -CONT <pid>

D. kill -TERM <pid>

Solution

1. Step 1: Recall kill command signals

   The kill command sends signals to processes; -STOP pauses, -CONT resumes.

2. Step 2: Identify pause signal

   Signal -STOP pauses the process without terminating it.

3. Final Answer:

   kill -STOP <pid> -> Option B

4. Quick Check:

   Pause process = kill -STOP [OK]

Hint: Use kill -STOP to pause a process [OK]

Common Mistakes:

• Using kill -9 which forcefully kills the process
• Confusing -CONT (resume) with pause
• Using kill -TERM which terminates the process

3. What will be the output of the command sequence below?

sleep 100 &
jobs
kill -STOP %1
jobs

medium

A. Shows the job stopped both times

B. Shows no jobs running

C. Shows the job running, then shows it stopped

D. Shows an error because kill -STOP is invalid

Solution

1. Step 1: Understand the commands

   sleep 100 & runs sleep in background; jobs lists jobs; kill -STOP %1 pauses job 1.

2. Step 2: Predict jobs output

   First jobs shows sleep running; after kill -STOP, jobs shows it stopped.

3. Final Answer:

   Shows the job running, then shows it stopped -> Option C

4. Quick Check:

   jobs before and after kill -STOP = running then stopped [OK]

Hint: jobs shows status; kill -STOP pauses job [OK]

Common Mistakes:

• Thinking kill -STOP kills the job
• Expecting no jobs after sleep &
• Believing kill -STOP is invalid

4. You run kill -STOP 1234 but the process does not pause. What is the most likely reason?

medium

A. You need to run the command as root

B. You used the wrong signal; should be kill -9

C. The process is already stopped

D. The process ID 1234 does not exist

Solution

1. Step 1: Check process existence

   If the process ID does not exist, kill commands have no effect.

2. Step 2: Consider other reasons

   Wrong signal or permissions cause errors, but no pause means no such process.

3. Final Answer:

   The process ID 1234 does not exist -> Option D

4. Quick Check:

   Nonexistent PID = no pause [OK]

Hint: Check if PID exists before sending signals [OK]

Common Mistakes:

• Assuming kill -9 pauses process
• Ignoring process existence
• Thinking root is always required

5. You want to temporarily pause a script running in the background, then resume it later. Which sequence of commands correctly achieves this?

hard

A. kill -STOP <pid> to pause, then kill -CONT <pid> to resume

B. kill -TERM <pid> to pause, then kill -STOP <pid> to resume

C. kill -9 <pid> to pause, then restart the script manually

D. kill -CONT <pid> to pause, then kill -STOP <pid> to resume

Solution

1. Step 1: Identify pause and resume signals

   kill -STOP pauses a process; kill -CONT resumes it.

2. Step 2: Verify command sequence

   Pause with kill -STOP, then resume with kill -CONT is correct.

3. Final Answer:

   kill -STOP <pid> to pause, then kill -CONT <pid> to resume -> Option A

4. Quick Check:

   Pause = kill -STOP, Resume = kill -CONT [OK]

Hint: Pause with STOP, resume with CONT signals [OK]

Common Mistakes:

• Using kill -9 which kills process
• Mixing up STOP and CONT signals
• Trying to resume with STOP signal