Same as STARTĦ) Displaying output in a user-defined format STIME: This points to the time the command was started.C: This refers to the %CPU or percentage of the CPU utilization of a process.PPID: This refers to the Parent Process ID.Let’s define a few new terms from the screenshot: The -f flag (full format) instructs the ps command to list detailed information about the processes. The -e flag tells the ps command to list all the processes If you wish to display the output in UNIX format, then execute the ps command with a combination of -ef flags ~]$ ps -ef START – This is the time the process started running.STAT – This points to the process state code e.g S (sleeping), Z (zombie) and R (Running).RSS – This is the size/amount of physical memory being used by a process.VSZ – This is the size of virtual memory of each process in kilobytes.%MEM – This is the % of the physical memory used up by the process.%CPU – This it the percentage CPU usage of each process.PID – This is the Process ID of the process.USER – This specifies the user running the process.The x flag lists processes that are usually started upon a system boot as well as background processes. It provides more detailed information associated with the running processes. The -u flag implies a user-oriented format. This, however, excludes the processes associated with a specific terminal. The -a flag instructs ps to display all the processes from all the users. To list the processes in BSD format, run the command $ ps -aux ~]$ ps -e 4) Displaying output in BSD format To get an overview of all the running processes on your Linux system use the -A flag as shown: ~]$ ps -AĪlternatively, you can also use the – e flag as shown. ~]$ 3) Displaying all the running processes on your system To list the processes associated with the terminal you are currently running, execute the command: ~]$ ps -T This is much like the listing the processes in the shell. CMD: Name of the command that started the process.Ģ) Listing processes associated with a terminal.TIME: This is the time / cumulative time that a process has run for.TTY: This refers to the terminal that started and is controlling the process.Mem: 3083924 2177300 906624 0 461344 837008Īlthough there are only 906624 bytes of RAM sitting completely unused at the moment, there are an additional 461344 bytes of buffers and 837008 bytes of cached data which can be made available more-or-less instantly if something more important (i.e., just about anything) needs the memory, giving me a total of 2204976 bytes actually available to me. That's the line which will tell you how much memory is actually tied up by running programs, ignoring what's being used for the moment by buffers and cache.įor example, my machine currently shows: total used free shared buffers cached You need to be looking at the second line of output from free, the one labeled -/+ buffers/cache. Linux is very aggressive about caching data from disk, even including "swapped out" virtual memory pages, in RAM and all that cached data is counted as "used" in free's first line, even though it can be made available again in a microsecond (or less, these days) if needed. Ignore the first line of output from free. Looks like you're running free, looking at the first line, and freaking out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |