Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How to run command in bash without saving it in history?

share|improve this question
Maybe duplicate :… – Luc M Feb 28 '11 at 19:07
up vote 52 down vote accepted

Add space before command. commands starting with a space do not put in history:

root@ubuntu-1010-server-01:~# echo foo
root@ubuntu-1010-server-01:~# history 
    1  echo foo
    2  history 
root@ubuntu-1010-server-01:~#  echo bar
root@ubuntu-1010-server-01:~# history 
    1  echo foo
    2  history 

man bash

         A  colon-separated  list of values controlling how commands are
         saved on the history list.  If  the  list  of  values  includes
         ignorespace,  lines  which begin with a space character are not
         saved in the history list.  A value of ignoredups causes  lines
         matching  the  previous history entry to not be saved.  A value
         of ignoreboth is shorthand for ignorespace and  ignoredups.   A
         value  of erasedups causes all previous lines matching the cur‐
         rent line to be removed from the history list before that  line
         is  saved.   Any  value  not  in the above list is ignored.  If
         HISTCONTROL is unset, or does not include a  valid  value,  all
         lines  read  by the shell parser are saved on the history list,
         subject to the value of HISTIGNORE.  The second and  subsequent
         lines  of a multi-line compound command are not tested, and are
         added to the history regardless of the value of HISTCONTROL.
share|improve this answer
Better than my answer of $HISTIGNORE would have been. +1 – Matt Simmons Feb 28 '11 at 14:12
learn something new every day. – David Rickman Feb 28 '11 at 15:29
I usually set this in /etc/profile as HISTCONTROL=ignoreboth and export the HISTCONTROL variable. – ewwhite May 15 '11 at 22:55
This doesn't seem to work for me? It seems to write to history, but just include the space in front. 486 echo test 487 history 488 echo testspace 489 history – Peter Jan 3 '13 at 13:45
Disregard that last comment, looks like it works in Ubuntu but not Debian/other OS's. – Peter Jan 5 '13 at 11:37

Also worth mentioning the trick to kill the current login session instead of normal exit (thus not giving a chance to save the history). This is especially useful when you login to a shared a/c, instead of remembering to prefix with a space, you could just end the session by killing it. The simplest way to kill is by running this command:

kill -9 0

Pid 0 always refers to the current process's PID, so you are basically sending a deadly kill signal to itself. I also often use this instead of exiting normally, as I often have hung sessions on normal exit, probably due to some misconfiguration.

share|improve this answer

Another solution is to set the history file to a directory:

export HISTFILE=/
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.