13,420
edits
Changes
→INVESTIGATION 2: MANAGING PROCESSES
# Issue the '''jobs''' command. What do you notice?<br>You should notice all commands are run in a group as just one process.<br><br>
# Issue the following Linux command to terminate the first job:<br><span style="color:blue;font-family:courier;font-weight:bold">kill %1</span><br><br>NOTE: If issuing the kill command does not work, then you would need to send a STRONGER signal<br>to "'''kill'''" (not "''SIGTERM'' - which is signal ''#15''") the process. The '''SIGKILL''' signal (signal '''#9''') would be required to do this<br>by issuing the '''kill''' command with the option: '''-9'''. By the way, the '''ctrl-c''' key combination sends the ''SIGINT''<br>(signal interupt - which is signal ''#2'') to terminate processes running in the ''foreground''.<br><br>
# Issue the '''jobs''' command and make certain there are no processes that are running in the background.<br><br>Let's terminate our Matrix Bash shell process by using the '''kill''' command using that process' '''PID'''.<br><br>
# Issue the following Linux command: <span style="color:blue;font-family:courier;font-weight:bold">ps</span><br><br>Note in the '''ps''' command output the PID of the process called '''bash'''.<br>
You will be using that PID when issuing the <u>next</u> Linux command.<br><br># Issue the following Linux command (using the bash process' PID number instead of "PID"):<br><span style="color:blue;font-family:courier;font-weight:bold">kill PID</span><br><br>What did you notice? It did not work since you need to send a STRONGER signal (eg. SIGKILL, not SIGTERM).<br><br>
# Issue the following Linux command (using the bash process' PID number instead of "PID"):<br><span style="color:blue;font-family:courier;font-weight:bold">kill -9 PID</span><br><br>What did you notice? You have been logged off your Matrix session!<br><br>
:In the next investigation, you will learn how to create aliases and view command history on your Matrix server.<br><br>