{"id":63077,"date":"2022-03-21T09:01:23","date_gmt":"2022-03-21T09:01:23","guid":{"rendered":"https:\/\/www.cryptocabaret.com\/?p=63077"},"modified":"2022-03-21T09:01:23","modified_gmt":"2022-03-21T09:01:23","slug":"my-favorite-linux-top-command-options","status":"publish","type":"post","link":"https:\/\/www.cryptocabaret.com\/?p=63077","title":{"rendered":"My favorite Linux top command options"},"content":{"rendered":"

My favorite Linux top command options<\/span>
\nDon Watkins<\/a><\/span>
\nMon, 03\/21\/2022 – 03:00<\/span><\/p>\n

\n
Up<\/div>\n
Register<\/a> or Login<\/a> to like.<\/div>\n<\/div>\n
\n

When I am checking out Linux systems (or even troubleshooting computers running other operating systems), I frequently use the top<\/code> command to check out the system’s RAM and CPU utilization. It provides me with information to assess the computer’s overall health. I learned about the top<\/code> command early in my Linux journey and have relied on it to give me a quick overview of what is happening on servers or other Linux systems, including Raspberry Pi. According to its man page, the top program provides a dynamic real-time view of a running system. It can display system summary information as well as a list of processes or threads currently being managed by the Linux kernel<\/em>.<\/p>\n

A quick overview is often all I need to determine what is going on with the system in question. But there is so much more to the top<\/code> command than meets the eye. Specific features of your top<\/code> command may vary depending on whose version (procps-ng, Busybox, BSD) you run, so consult the man page for details.<\/p>\n

To launch top<\/code>, type it into your terminal:<\/p>\n

\n$ <\/span>top<\/code><\/span><\/pre>\n
Running processes are displayed below the table heading on the top<\/code> screen, and system statistics are shown above it.<\/p>\n
\n
Top 05:31<\/span>:09 up 55<\/span> min,3<\/span> users<\/span>,load average: 0.54<\/span>, 0.38<\/span>, 0.46<\/span>
\nTasks: 469<\/span> total, 1<\/span> running, 468<\/span> sleeping, \u00a00<\/span> stopped, 0<\/span> zombie
%<\/span>Cpu(<\/span>s)<\/span>: 1.0<\/span> us, 0.4<\/span> sy, 0.0<\/span> ni, 98.6<\/span> id<\/span>, 0.1<\/span> wa, 0.0<\/span> hi,0.0<\/span> si,0.0<\/span> st
\nMiB Mem : 32116.1<\/span> total, \u00a020256.5<\/span> free<\/span>, 6376.3<\/span> used, 5483.3<\/span> buff\/<\/span>cache
\nMiB Swap: 0.0<\/span> total, \u00a00.0<\/span> free<\/span>, \u00a0 \u00a0 \u00a00.0<\/span> used. \u00a025111.4<\/span> avail Mem \u00a0

\n\u00a0PID USER \u00a0PR NI \u00a0 VIRT \u00a0 \u00a0RES \u00a0 SHR S %<\/span>CPU %<\/span>MEM \u00a0 \u00a0TIME+ COMMAND \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 
2566<\/span> don \u00a0 20<\/span> \u00a00<\/span> \u00a011.9g 701300<\/span> 78848<\/span> S \u00a03.3<\/span> \u00a02.1<\/span> \u00a02<\/span>:03.80<\/span> firefox-bin
1606<\/span> don \u00a0 20<\/span> \u00a00<\/span> \u00a024.2g \u00a088084<\/span> \u00a04512<\/span> S \u00a02.0<\/span> \u00a00.3<\/span> \u00a00<\/span>:39.59<\/span> elisa
1989<\/span> don \u00a0 20<\/span> \u00a00<\/span> 894236<\/span> 201580<\/span> 23536<\/span> S \u00a02.0<\/span> \u00a00.6<\/span> \u00a00<\/span>:46.12<\/span> stopgo-java
5483<\/span> don \u00a0 20<\/span> \u00a00<\/span> \u00a024.5g 239200<\/span> 20868<\/span> S \u00a01.3<\/span> \u00a00.7<\/span> \u00a00<\/span>:26.54<\/span> Isolated Web Co
5726<\/span> don \u00a0 20<\/span> \u00a00<\/span> 977252<\/span> 228012<\/span> 44472<\/span> S \u00a01.3<\/span> \u00a00.7<\/span> \u00a00<\/span>:41.25<\/span> pulseaudio<\/div><\/div><\/pre>\n
Press the Z<\/strong> key to change the color of the output. I find this makes the output a little easier on the eyes.<\/p>\n
Press the 1<\/strong> key to see a graphical representation of each CPU core on the system. Press 1<\/strong> repeatedly to assess core statistics for your CPU cores.<\/p>\n
You can display memory usage graphically by invoking the top<\/code> command and then pressing the m<\/strong> key.<\/p>\n<\/p>\n
\n
More Linux resources<\/div>\n
\n
Linux commands cheat sheet<\/a><\/div>\n
Advanced Linux commands cheat sheet<\/a><\/div>\n
Free online course: RHEL technical overview<\/a><\/div>\n
Linux networking cheat sheet<\/a><\/div>\n
SELinux cheat sheet<\/a><\/div>\n
Linux common commands cheat sheet<\/a><\/div>\n
What are Linux containers?<\/a><\/div>\n
Our latest Linux articles<\/a><\/div>\n<\/p><\/div>\n<\/p><\/div>\n
Useful top options<\/h2>\n
If you’re looking only for the processes started by a specific user, you can get that information with the -u<\/code> option:<\/p>\n
\n$ <\/span>top -u<\/span> 'username'<\/span><\/code><\/span><\/pre>\n
To get a list of idle processes on your system, use the -i<\/code> option:<\/p>\n
\n$ <\/span>top -i<\/span><\/code><\/span><\/pre>\n
You can set the update interval to an arbitrary value in seconds. The default value is three seconds. Change it to five like this:<\/p>\n
\n$ <\/span>top -d<\/span> 5<\/span><\/code><\/span><\/pre>\n
You can also run top<\/code> on a timer. For instance, the following command sets the number of iterations to two and then exits:<\/p>\n
\n$ <\/span>top -n<\/span> 2<\/span><\/code><\/span><\/pre>\n
Locate a process with top<\/h2>\n
Press Shift+L<\/strong> to locate a process by name. This creates a prompt just above the bold table header line. Type in the name of the process you’re looking for and then press Enter<\/strong> or Return<\/strong> to see the instances of that process highlighted in the newly sorted process list.<\/p>\n
Stopping a process with top<\/h2>\n
You can stop or “kill” a running process with top<\/code>, too. First, find the process you want to stop using either Shift+L<\/strong> or pgrep<\/code>. Next, press K<\/strong> and enter the process ID you want to stop. The default value is whatever is at the top of the list, so be sure to enter the PID you want to stop before pressing Enter<\/strong>, or you may stop a process you didn’t intend to.<\/p>\n
\n
  \"top<\/div>\n<\/article>\n
Top top<\/h2>\n
There are many iterations of the top<\/code> command, including htop<\/code>, atop<\/code>, btop<\/code>, and ttop<\/code>. There are specialized top<\/code> commands, too, like powertop<\/code> for power usage and ntop<\/code> for networks. What’s your favorite top<\/code>?<\/p>\n<\/div>\n
\n
A quick overview is often all I need to determine what is going on with my Linux system. But there is so much more to the top command than meets the eye.<\/p>\n<\/div>\n
\n
\n
  \"Command<\/div>\n
Image by: <\/span><\/p>\n
Opensource.com<\/p>\n<\/div>\n<\/article>\n<\/div>\n
\n
Linux<\/a><\/div>\n
Command line<\/a><\/div>\n<\/p><\/div>\n
What to read next<\/div>\n

\n        \"Creative<\/a>This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.<\/div>\n
\n
\n
Register<\/a> or Login<\/a> to post a comment.<\/div>\n<\/p><\/div>\n<\/section>\n
Powered by WPeMatico<\/a><\/small><\/p>\n","protected":false},"excerpt":{"rendered":"
My favorite Linux top command options Don Watkins Mon, 03\/21\/2022 – 03:00 Up Register or Login to like. When I am checking out Linux systems (or even troubleshooting computers running other operating systems), I frequently use the top command to check out the system’s RAM and CPU utilization. It provides me with information to assess […]<\/p>\n","protected":false},"author":1,"featured_media":63078,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[307],"tags":[],"class_list":["post-63077","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-open-source"],"_links":{"self":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts\/63077","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=63077"}],"version-history":[{"count":0,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts\/63077\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/media\/63078"}],"wp:attachment":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=63077"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=63077"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=63077"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}