Execute a command without saving it in the history
$ echo this goes to history
this goes to history
$ echo this wont go to history
this wont go to history
$ history
1 echo this goes to history
2 history
5 Alternatives + Submit Alt
-
Sometimes you don't want to leave history, because of passwords use or somethink like. I think it help.
7cat | bash -
wget --user=username --password="$password" http://example.org/Instead of hiding commands entirely from history, I prefer to use "read" to put the password into a variable, and then use that variable in the commands instead of the password. Without the "-e" and "-s" it should work in any bourne-type shell, but the -s is what makes sure the password doesn't get echoed to the screen at all. (-e makes editing work a bit better)4read -e -s -p "Password: " password -
<space>secret_command;export HISTCONTROL=This will make "secret_command" not appear in "history" list.3export HISTCONTROL=ignorespace -
Put a space in front of your command on the command line and it will not be logged as part of your command line history. Show Sample Output
1<space> secret -p password -
Yes, by correctly setting the HIST* variables you can make certain commands not saved in history. But that's complicated and easy to make a mistake. If you set HISTFILE= to blank, nothing in your current shell session will be saved in history. Although this is not a precise answer to the subject, but it's very simple.
1HISTFILE= ; your_secret_command
What do you think?
Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?
You must be signed in to comment.
What's this?
commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
Similar Commands
Stay in the loop…
- Follow the Tweets.
-
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10 - Subscribe to the feeds.
-
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
- » all commands
- » commands with 3 up-votes (commandlinefu3)
- » commands with 10 up-votes (commandlinefu10)
kill -9 $$echo export HISTIGNORE="[ \t]*" >> .bashrcwill appear in the history :) You should do<space> history -d NWhere N is the postion export HISTIGNORE="[ \t]*"