Differences

This shows you the differences between two versions of the page.

Link to this comparison view

iot:labs:02 [2015/07/24 18:51]
alexandru.radovici
iot:labs:02 [2017/09/11 09:33] (current)
alexandru.radovici created
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 53: Line 53:
  
 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.
iot/labs/02.1437753086.txt.gz ยท Last modified: 2015/07/24 18:51 by alexandru.radovici
CC Attribution-Share Alike 3.0 Unported
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0