


How to let the history command display date and time in Linux
The history command stores all commands executed by bash on the terminal into the .bash_history file to help us review the commands previously executed by the user. This article mainly introduces the method of letting the history command display the date and time. Friends who need it can refer to it. I hope it can help everyone.
By default, the history command directly displays the commands executed by the user without outputting the date and time when the command was run, even if the history command records this time.
When you run the history command, it will check an environment variable called HISTTIMEFORMAT. This environment variable specifies how to format the output of the time recorded in the history command.
If the value is null or not set at all, it will be the same as most systems display by default, and the date and time will not be displayed.
HISTTIMEFORMAT Use strftime to format display times (strftime - Converts dates and times to strings). The history command outputs the date and time to help you track down the problem more easily.
%T: Replaced with time (%H:%M:%S).
%F : Equivalent to %Y-%m-%d (ISO 8601:2000 standard date format).
The following is the default output of the history command.
# history yum install -y mysql-server mysql-client service mysqld start sysdig proc.name=sshd sysdig -c topprocs_net sysdig proc.name=sshd sysdig proc.name=sshd | more sysdig fd.name=/var/log/auth.log | more sysdig fd.name=/var/log/mysqld.log sysdig -cl sysdig -i httplog sysdig -i proc_exec_time sysdig -i topprocs_cpu sysdig -c topprocs_cpu sysdig -c tracers_2_statsd sysdig -c topfiles_bytes sysdig -c topprocs_cpu sysdig -c topprocs_cpu "fd.name contains sshd" sysdig -c topprocs_cpu "proc.name contains sshd" csysdig sysdig -c topprocs_cpu rpm --import https://s3.amazonaws.com/download.draios.com/DRAIOS-GPG-KEY.public curl -s -o /etc/yum.repos.d/draios.repo http://download.draios.com/stable/rpm/draios.repo yum install -y epel-release yum update yum makecache yum -y install kernel-devel-$(uname -r) yum -y install sysdig sysdig yum install httpd mysql service httpd start
There are three different ways to set environment variables based on needs.
Temporarily set the environment variables of the current user
Permanently set the environment variables of the current/other users
Permanently set environment variables for all users
Note: Don’t forget to add a space before the last single quote, otherwise the output will be very confusing.
Method 1:
Run the following command to temporarily set the HISTTIMEFORMAT variable for the current user. This will take effect until the next reboot.
# export HISTTIMEFORMAT='%F %T '
Method 2:
Add the HISTTIMEFORMAT variable to the .bashrc or .bash_profile file to make it permanent.
# echo 'HISTTIMEFORMAT="%F %T "' >> ~/.bashrc
or
# echo 'HISTTIMEFORMAT="%F %T "' >> ~/.bash_profile
Run the following command to make the changes in the file take effect.
#source~/.bashrc
or
#source~/.bash_profile
Method 3:
Change HISTTIMEFORMAT Add the variable to the /etc/profile file to make it permanent for all users.
# echo 'HISTTIMEFORMAT="%F %T "' >> /etc/profile
Run the following command to make the changes in the file take effect.
#source/etc/profile
The output result is:
# history 2017-08-16 15:30:15 yum install -y mysql-server mysql-client 2017-08-16 15:30:15 service mysqld start 2017-08-16 15:30:15 sysdig proc.name=sshd 2017-08-16 15:30:15 sysdig -c topprocs_net 2017-08-16 15:30:15 sysdig proc.name=sshd 2017-08-16 15:30:15 sysdig proc.name=sshd | more 2017-08-16 15:30:15 sysdig fd.name=/var/log/auth.log | more 2017-08-16 15:30:15 sysdig fd.name=/var/log/mysqld.log 2017-08-16 15:30:15 sysdig -cl 2017-08-16 15:30:15 sysdig -i httplog 2017-08-16 15:30:15 sysdig -i proc_exec_time 2017-08-16 15:30:15 sysdig -i topprocs_cpu 2017-08-16 15:30:15 sysdig -c topprocs_cpu 2017-08-16 15:30:15 sysdig -c tracers_2_statsd 2017-08-16 15:30:15 sysdig -c topfiles_bytes 2017-08-16 15:30:15 sysdig -c topprocs_cpu 2017-08-16 15:30:15 sysdig -c topprocs_cpu "fd.name contains sshd" 2017-08-16 15:30:15 sysdig -c topprocs_cpu "proc.name contains sshd" 2017-08-16 15:30:15 csysdig 2017-08-16 15:30:15 sysdig -c topprocs_cpu 2017-08-16 15:30:15 rpm --import https://s3.amazonaws.com/download.draios.com/DRAIOS-GPG-KEY.public 2017-08-16 15:30:15 curl -s -o /etc/yum.repos.d/draios.repo http://download.draios.com/stable/rpm/draios.repo 2017-08-16 15:30:15 yum install -y epel-release 2017-08-16 15:30:15 yum update 2017-08-16 15:30:15 yum makecache 2017-08-16 15:30:15 yum -y install kernel-devel-$(uname -r) 2017-08-16 15:30:15 yum -y install sysdig 2017-08-16 15:30:15 sysdig 2017-08-16 15:30:15 yum install httpd mysql 2017-08-16 15:30:15 service httpd start
Related recommendations:
How to Vue-cli is transformed into a history mode that supports multiple pages
Detailed explanation of the History mode in HTML5
The above is the detailed content of How to let the history command display date and time in Linux. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











The five basic components of the Linux system are: 1. Kernel, 2. System library, 3. System utilities, 4. Graphical user interface, 5. Applications. The kernel manages hardware resources, the system library provides precompiled functions, system utilities are used for system management, the GUI provides visual interaction, and applications use these components to implement functions.

vscode built-in terminal is a development tool that allows running commands and scripts within the editor to simplify the development process. How to use vscode terminal: Open the terminal with the shortcut key (Ctrl/Cmd). Enter a command or run the script. Use hotkeys (such as Ctrl L to clear the terminal). Change the working directory (such as the cd command). Advanced features include debug mode, automatic code snippet completion, and interactive command history.

To view the Git repository address, perform the following steps: 1. Open the command line and navigate to the repository directory; 2. Run the "git remote -v" command; 3. View the repository name in the output and its corresponding address.

Writing code in Visual Studio Code (VSCode) is simple and easy to use. Just install VSCode, create a project, select a language, create a file, write code, save and run it. The advantages of VSCode include cross-platform, free and open source, powerful features, rich extensions, and lightweight and fast.

Although Notepad cannot run Java code directly, it can be achieved by using other tools: using the command line compiler (javac) to generate a bytecode file (filename.class). Use the Java interpreter (java) to interpret bytecode, execute the code, and output the result.

The main uses of Linux include: 1. Server operating system, 2. Embedded system, 3. Desktop operating system, 4. Development and testing environment. Linux excels in these areas, providing stability, security and efficient development tools.

VS Code One-step/Next step shortcut key usage: One-step (backward): Windows/Linux: Ctrl ←; macOS: Cmd ←Next step (forward): Windows/Linux: Ctrl →; macOS: Cmd →

Causes and solutions for the VS Code terminal commands not available: The necessary tools are not installed (Windows: WSL; macOS: Xcode command line tools) Path configuration is wrong (add executable files to PATH environment variables) Permission issues (run VS Code as administrator) Firewall or proxy restrictions (check settings, unrestrictions) Terminal settings are incorrect (enable use of external terminals) VS Code installation is corrupt (reinstall or update) Terminal configuration is incompatible (try different terminal types or commands) Specific environment variables are missing (set necessary environment variables)
