Using Bash History More Efficiently: HISTCONTROL

 in

Using the HISTCONTROL variable you can control how bash stores your command history. You can tell it to ignore duplicate commands and/or to ignore commands that have leading whitespace.

When working at the command line we often end up executing some commands multiple times. The default history size is 500, too many duplicates of the same commands can fill up your history and leave you with a less then useful history. You can of course increase the size of your history list using HISTSIZE or HISTFILESIZE.

Another alternative is to tell bash not to store duplicates. This is done with the HISTCONTROL variable. HISTCONTROL controls how bash stores command history. Currently there are two possible flags: ignorespace and ignoredups. The ignorespace flag tells bash to ignore commands that start with spaces. The other flag, ignoredups, tells bash to ignore duplicates. You can concatenate and separate the values with a colon, ignorespace:ignoredups, if you wish to specify both values, or you can just specify ignoreboth.

You can set the flags in your ~/.bashrc file or in the global /etc/bash.bashrc file. The following command would append it to your ~/.bashrc file:

  $ echo "HISTCONTROL=ignoreboth" >>~/.bashrc

Now logout and login, type some commands, try the same command numerous times. Now check your history using the up arrow or do:

  $ history|more

You shouldn't see any duplicates in your history.

The history control option, ignorespace, is useful for executing commands that you don't want to record in your command history.

______________________

Cheng Renquan, Shenzhen, China

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

you have bash 3

Yahym's picture

you can use:

export HISTCONTROL=erasedups

and you'll never have a duplicate entry in the history.

No need to log out and in

Will Warren's picture

you can just do

# source ~/.bashrc

instead of logging out and in, it just saves a little time :D

Source Shortcut

ervt's picture

Or just simply do: . ~/.bashrc
The early Unix folks must have run this command a lot.

Or even better

stevenworr's picture

Add this to your ~/.bash_profile

export HISTCONTROL=ignoreboth

Then there's not need to set a local copy in each subshell. Each subshell would just inherit it.

Steven W. Orr

Webinar
One Click, Universal Protection: Implementing Centralized Security Policies on Linux Systems

As Linux continues to play an ever increasing role in corporate data centers and institutions, ensuring the integrity and protection of these systems must be a priority. With 60% of the world's websites and an increasing share of organization's mission-critical workloads running on Linux, failing to stop malware and other advanced threats on Linux can increasingly impact an organization's reputation and bottom line.

Learn More

Sponsored by Bit9

Webinar
Linux Backup and Recovery Webinar

Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.

In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.

Learn More

Sponsored by Storix