Differences
This shows you the differences between two versions of the page.
|
iot:labs:02 [2015/07/22 12:43] madalina.tanea [Lab 02. Linux] |
iot:labs:02 [2017/09/11 09:33] (current) alexandru.radovici created |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Lab 02. Linux ====== | + | ====== Lab 2: Linux ====== |
| Embeded boards run Linux, this is why when interracting with them you might need some basic notions concerning this operating system in case you haven't come across it so far. | Embeded boards run Linux, this is why when interracting with them you might need some basic notions concerning this operating system in case you haven't come across it so far. | ||
| Line 44: | Line 44: | ||
| By using the //htop// command you can see real-time all the processes that run on your board. Once you entered the command you will notice that the prompt does not appear, that is because you cannot enter another command until you are finished with displaying the processes. So, if you want to go back to what you were doing, just hit the //q// key. | By using the //htop// command you can see real-time all the processes that run on your board. Once you entered the command you will notice that the prompt does not appear, that is because you cannot enter another command until you are finished with displaying the processes. So, if you want to go back to what you were doing, just hit the //q// key. | ||
| - | {{ :iot:labs:htop.png?500 |}} | + | {{ :iot2015:labs:htop.png?500 |}} |
| For each process displayed, you can see its PID (Process ID), the user who launched the process, how much CPU and memory it is using, the command that started the process and other information. | For each process displayed, you can see its PID (Process ID), the user who launched the process, how much CPU and memory it is using, the command that started the process and other information. | ||
| Line 50: | Line 50: | ||
| ===== kill ===== | ===== kill ===== | ||
| - | We know that you can use //htop// to find a process' ID in order to be able to interact with it. //kill// is the command that allows us to interact with another process. | + | You know that you can use //htop// to find a process' ID in order to be able to interact with it. //kill// is the command that allows us to interact with another process. |
| Two processes can interact by using signals. A signal is a number a process sends to another. Both processes know that each number represents an action. you can refer to a signal either by the number or by its name. | Two processes can interact by using signals. A signal is a number a process sends to another. Both processes know that each number represents an action. you can refer to a signal either by the number or by its name. | ||
| - | {{ :iot:labs:kill.png?500 |}} | + | {{ :iot2015:labs:kill.png?500 |}} |
| The format of the //kill// command is the following: //kill -signal pid//, where signal is the number representing the action you want to process to do and pid is the process ID. | The format of the //kill// command is the following: //kill -signal pid//, where signal is the number representing the action you want to process to do and pid is the process ID. | ||
