Set Date and Time for Each Command You Execute in Bash History

By default, all commands executed by Bash on the command line are stored in history buffer or recorded in a file called ~/.bash_history. This means that a system administrator can view a list of commands executed by users on the system or a user can view his/her command history using the history command like so.

$ history
Linux History Command
Linux History Command

From the output of the history command above, the date and time when a command was executed is not shown. This is the default setting on most if not all Linux distributions.

In this article, we will explain how you can configure time stamp information when each command in the Bash history was executed to be displayed.

The date and time associated with each history entry can be written to the history file, marked with the history comment character by setting the HISTTIMEFORMAT variable.

There are two possible ways of doing this: one does it temporarily while the other makes it permanent.

To set HISTTIMEFORMAT variable temporarily, export it as below on the command line:

$ export HISTTIMEFORMAT='%F %T'

In the export command above, the time stamp format:

  1. %F – expands to full date same, as %Y-%m-%d (year-month-date).
  2. %T – expands to time; same as %H:%M:%S (hour:minute:seconds).

Read through the date command man page for additional usage information:

$ man date

Then check your command history as follows:

$ history 
Display Linux Command History with Date and Time
Display Linux Command History with Date and Time

However, if you want to configure this variable permanently, open the file ~/.bashrc with your favorite editor:

$ vi ~/.bashrc

And add the line below in it (you mark it with a comment as your own configuration):

#my config
export HISTTIMEFORMAT='%F %T'

Save the file and exit, afterwards, run the command below to effect the changes made to the file:

$ source ~/.bashrc

That’s all! Do share with us any interesting history command tips and tricks or your thoughts about this guide via the comment section below.

Hey TecMint readers,

Exciting news! Every month, our top blog commenters will have the chance to win fantastic rewards, like free Linux eBooks such as RHCE, RHCSA, LFCS, Learn Linux, and Awk, each worth $20!

Learn more about the contest and stand a chance to win by sharing your thoughts below!

Ravi Saive
I am an experienced GNU/Linux expert and a full-stack software developer with over a decade in the field of Linux and Open Source technologies

Each tutorial at TecMint is created by a team of experienced Linux system administrators so that it meets our high-quality standards.

Join the TecMint Weekly Newsletter (More Than 156,129 Linux Enthusiasts Have Subscribed)
Was this article helpful? Please add a comment or buy me a coffee to show your appreciation.

19 Comments

Leave a Reply
    • @Gaspar,

      Remove the following line from your /.bashrc file to print date and time in history command.

      export HISTTIMEFORMAT='%F %T'
      
      Reply
  1. Can we set this if we don’t have root privilege on the server? I tried doing it by exporting as shown above .. it didn’t give me any error but it didn’t show the time and date in history

    Reply
  2. Hello,
    Thanks million for your efforts and your great post.
    I want to show ip address (of the user that executed the command) in history command. How can i do that?

    Second question
    when i ssh to my linux machine with putty and suddenly my windows restart (for any reason) there is no history in next ssh
    but if i exit from putty with command “exit” in my server history will be saved for next ssh login.
    how can i set that each command to be saved even if putty closed abnormal?

    Reply
  3. Modifying bash_history file won’t let you use other options, like re-running some command from history by using ! char at the beginning. IMHO, good, but not ideal

    Reply
    • @Marek

      You actually do not have to modify the bash_history file. This method simply adds the timestamp to a command entry in it, and you can re-run commands as usual.

      Reply
  4. Just don’t forget to update your actual system time to correlate with your IRL time. Usually the system’s (server) time is not the same as the one where you’re actually working from.

    It’s just easier, not that it really matters.

    Reply

Got Something to Say? Join the Discussion...

Thank you for taking the time to share your thoughts with us. We appreciate your decision to leave a comment and value your contribution to the discussion. It's important to note that we moderate all comments in accordance with our comment policy to ensure a respectful and constructive conversation.

Rest assured that your email address will remain private and will not be published or shared with anyone. We prioritize the privacy and security of our users.