Linux Command Line of history, historylinux

Linux Command Line of history, historylinux

1. Use HISTTIMEFORMAT to display the timestamp
After you execute the history command from the command line, only the serial number of the executed command and the command itself are displayed. To view the timestamp of the command history, run the following command:

# Export HISTTIMEFORMAT = '% F % t'
# History | more
1 2008-08-05 19:02:39 service network restart
2 19:02:39 exit
3 2008-08-05 19:02:39 id
4 2008-08-05 19:02:39 cat/etc/redhat-release

Use Ctrl + R to search for history
Ctrl + R is a frequently used shortcut key. This shortcut allows you to search for command history, which is useful when you want to execute a command repeatedly. After finding the command, you can usually press the Enter key to execute the command. If you want to adjust the command and then execute it, you can click the left or right arrow keys.

# [Press Ctrl + R from the command prompt, which will display the reverse-I-search prompt]
(Reverse-I-search) 'red': cat/etc/redhat-release
[Note: Press enter when you see your command, which will execute the command from the history]
# Cat/etc/redhat-release
Fedora release 9 (Sulphur)

Repeat the previous command
You can run the previous command again in four ways:

Use the up arrow key and press enter to execute.
Press !! And press enter to execute.
Enter! -1 and press enter to execute.
Press Ctrl + P and press Enter.
Execute a specified command from the command history
In the following example, if you want to repeat 4th commands, You can execute them! 4:

# History | more
1 service network restart
2 exit
3 id
4 cat/etc/redhat-release
#! 4
Cat/etc/redhat-release
Fedora release 9 (Sulphur)

Execute previous commands by specifying keywords
In the example below, enter! Ps and press Enter. The following command is executed to start with ps:

#! Ps
Ps aux | grep yp
Root 16947 0.0 0.1 36516 1264? Sl ypbind
Root 17503 0.0 0.0 4124 740 pts/0 S + grep yp

Use HISTSIZE to control the total number of historical Command records
Append the following two lines to the. bash_profile file and log on to the bash shell again. The number of command history records will change to 450:

# Vi ~ /. Bash_profile
History Size = 450
HISTFILESIZE = 450

Use HISTFILE to change the name of a historical file
By default, the command history is stored in ~ /. Bash_history file. Add the following content to the. bash_profile file and log on to the bash shell again. The. commandline_warrior command history will be stored:

# Vi ~ /. Bash_profile
HISTFILE =/root/. commandline_warrior

Use HISTCONTROL to remove consecutive duplicate entries from the command history
In the following example, the pwd command is executed three times in a row. After history is executed, you will see three duplicate entries. To remove these duplicate entries, you can set HISTCONTROL to ignoredups:

# Pwd
# Pwd
# Pwd
# History | tail-4
44 pwd
45 pwd
46 pwd [Note that there are three pwd commands in history, after executing pwd 3 times as shown above]
47 history | tail-4
# Export HISTCONTROL = ignoredups
# Pwd
# Pwd
# Pwd
# History | tail-3
56 export HISTCONTROL = ignoredups
57 pwd [Note that there is only one pwd command in the history, even after executing pwd 3 times as shown above]
58 history | tail-4

Use HISTCONTROL to clear duplicate entries in the history of the entire command
In the previous example, ignoredups can only remove consecutive duplicate entries. To clear duplicate entries in the history of the entire command, you can set HISTCONTROL to erasedups:

# Export HISTCONTROL = erasedups
# Pwd
# Service httpd stop
# History | tail-3
38 pwd
39 service httpd stop
40 history | tail-3
# Ls-ltr
# Service httpd stop
# History | tail-6
35 export HISTCONTROL = erasedups
36 pwd
37 history | tail-3
38 ls-ltr
39 service httpd stop
[Note that the previous service httpd stop after pwd got erased]
40 history | tail-6

Use HISTCONTROL to force history not to remember specific commands
Set HISTCONTROL to ignorespace and enter a space before the command you do not want to remember:

# Export HISTCONTROL = ignorespace
# Ls-ltr
# Pwd
# Service httpd stop [Note that there is a space at the beginning of service, to ignore this command from history]
# History | tail-3
67 ls-ltr
68 pwd
69 history | tail-3
Use the-c option to clear all command history
To clear all command history, run the following command:

# History-c

Command replacement
In the following example ,!! : $ Get the parameters of the previous command for the current command:

# Ls anaconda-ks.cfg
Anaconda-ks.cfg
# Vi !! : $
Vi anaconda-ks.cfg

In the following example ,! ^ Obtain the first parameter from the previous command:

# Cp anaconda-ks.cfg anaconda-ks.cfg.bak
Anaconda-ks.cfg
# Vi-5! ^
Vi anaconda-ks.cfg

Replaces the specified parameter with a specific command.
In the example below ,! Cp: 2 search for a command starting with cp from the command history and obtain its second parameter:

# Cp ~ /Longname.txt/really/a/very/long/path/long-filename.txt
# Ls-l! Cp: 2
Ls-l/really/a/very/long/path/long-filename.txt

In the following example ,! Cp: $ get the last parameter of the cp command:

# Ls-l! Cp: $
Ls-l/really/a/very/long/path/long-filename.txt

Disable history with HISTSIZE
If you want to disable history, you can set HISTSIZE to 0:

# Export HISTSIZE = 0
# History
# [Note that history did not display anything]

Use HISTIGNORE to ignore specific commands in history
In the following example, commands such as pwd, ls, and ls-ltr are ignored:

# Export HISTIGNORE = "pwd: ls-ltr :"
# Pwd
# Ls
# Ls-ltr
# Service httpd stop
# History | tail-3
79 export HISTIGNORE = "pwd: ls-ltr :"
80 service httpd stop
81 history
[Note that history did not record pwd, ls and ls-ltr]

Linux history command

Open the. bashrc File
Input:
HISTSIZE = 1000 (or the number you want)
Save
Logout and login again

Ask how the linux history command displays all historical records

All commands are displayed by default. If not, open the. bash_history file in the main directory of the user.
Vi ~ /. Bash_history so that all the commands of the current user can be seen. Of course, history stores your latest N commands (default value: 200, which can be modified through parameters)