{"id":17623,"date":"2022-06-04T05:21:02","date_gmt":"2022-06-04T05:21:02","guid":{"rendered":"https:\/\/linuxways.net\/?p=17623"},"modified":"2022-09-05T18:06:37","modified_gmt":"2022-09-05T18:06:37","slug":"how-to-check-your-command-history-in-ubuntu-20-04","status":"publish","type":"post","link":"https:\/\/linuxways.net\/de\/centos\/how-to-check-your-command-history-in-ubuntu-20-04\/","title":{"rendered":"How to Check Your Command History in Ubuntu 20.04"},"content":{"rendered":"

In their day-to-day operations, system administrators can execute countless commands on the servers to accomplish their goals. They could be running hundreds of commands in each session, and each session could differ from the last. This makes it very hard to remember all of the commands you\u2019ve executed in the past. But fret not, unknown to many people, whenever they are typing away at their terminal, Linux is recording all of the executed commands in a file.<\/p>\n

In this guide, I will walk you through the commands needed to look up our command history and reuse commands from there. While you get used to these commands, ascertain that you don\u2019t unintentionally execute a command that could cause issues for you. That said, take your time with these commands and practice them in a sandbox or virtual machine, if possible before you execute them in a live environment.<\/p>\n

Though these commands will work with most Linux distributions, for the purposes of this guide, I will show you these commands using Ubuntu 20.04.<\/p>\n

Scrolling through recent commands<\/h2>\n

The simplest way to lookup your commands is to use the up and the down arrow keys in the terminal. You can cycle through recent commands like this.<\/p>\n

<\/p>\n

When you find your desired command, all you have to do is press \u201cEnter\u201d.<\/p>\n

\u201cHistory\u201d command<\/h2>\n

Running the \u201chistory\u201d command in your terminal simply lists the last thousand commands executed in the terminal. You get each command prefixed with a number.<\/p>\n

$history<\/em><\/strong><\/pre>\n
<\/p>\n
Running the history command with the \u201cx\u201d number after it will list the last \u201cx\u201d commands executed. Like if we run the following, we get the last 2 commands executed.<\/p>\n
$history 2\u00a0<\/em><\/strong><\/pre>\n
<\/p>\n
You can change the number to any number you desire, e.g., 20, 30, 40 or anything.<\/p>\n
Executing a previous command<\/h2>\n
Now that we know about the \u201chistory\u201d command, you can simply re-execute a command using the number before it, as such. Let’s run history.<\/p>\n
<\/p>\n
Now out of all these commands, say I want to run the second command. All I need to do is get the number and run it like this:<\/p>\n
$!2<\/em><\/strong><\/pre>\n
<\/p>\n
Please remember that there is no space between the exclamation mark and the number.<\/p>\n
Enhanced search using grep<\/h2>\n
Up till now, we have been using simple commands as an example. Let\u2019s say you are working with lengthy commands and you only partially remember them. In order to find out all of the commands using a specific keyword, you can use the grep command in conjunction with history to pull up all relevant commands.<\/p>\n
Let\u2019s try pulling up commands where our command contains \u201c.com\u201d in it somewhere:<\/p>\n
$history | grep .com<\/em><\/strong><\/pre>\n
<\/p>\n
Here you will see your keyword highlighted in red.<\/p>\n
Using the built-in reverse search<\/h2>\n
Another way you can search for previously used commands is through the reverse search built into the terminal. To get to it, all you need to do is just press \u201cCtrl + r\u201d.<\/p>\n
Doing so, you will see your terminal get updated to:<\/p>\n
<\/p>\n
Now you can start typing your desired keyword and you will see the terminal returning with relevant matches. So, let\u2019s try to go back to the start and pull up hostname related commands.<\/p>\n
<\/p>\n
By pressing \u201cCtrl + r\u201d again you will cycle through all the results.<\/p>\n
<\/p>\n
Now in order to run any of these commands, you can press the \u201cEnter\u201d key to execute the command of your choice.<\/p>\n
<\/p>\n
Quickly executing the previous command<\/h2>\n
With practice comes enough confidence to remember the last command you\u2019ve executed. If you do remember the last command and know that it won\u2019t create any issues for you, you can quickly run it again with:<\/p>\n
$!!<\/em><\/strong><\/pre>\n
<\/p>\n
As you can see here I ran a simple \u201cls\u201d. Running \u201c!!\u201d tells you which command was run last and then executes it again. Now at times, it might be a command which requires elevated privileges, you can run that command as:<\/p>\n
$sudo !!<\/em><\/strong><\/pre>\n
<\/p>\n
Excluding commands from history<\/h2>\n
Now if you want to keep your commands from being included in the terminal history, you can add a space before it and the terminal will not save it.<\/p>\n
<\/p>\n
As you can see, I executed \u201cls\u201d after \u201chostnamectl\u201d, but when I pulled up the history, the \u201cls\u201d command at the second last place is not included in the history.<\/p>\n
Conclusion<\/h2>\n
With some practice, these commands become instinctive to use in your daily operations and can make your time with the terminal more effective and efficient. Through these commands, you get the ability to identify and re-execute a rarely used command, or a command that was difficult to arrange\/remember in the first place.<\/p>\n
As always, if you run into any issues with these commands or want to know more about them, feel free to drop us a comment below and we\u2019ll walk you through any issue or error.<\/p>","protected":false},"excerpt":{"rendered":"
In their day-to-day operations, system administrators can execute countless commands on the servers to accomplish their goals. They could be running hundreds of commands in each session, and…<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-17623","post","type-post","status-publish","format-standard","hentry","category-centos"],"_links":{"self":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/17623","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/comments?post=17623"}],"version-history":[{"count":0,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/17623\/revisions"}],"wp:attachment":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/media?parent=17623"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/categories?post=17623"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/tags?post=17623"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}