12-15-2010
Bash keeps it's history internally until it exits. This is why your .bash_history can be empty while you see old commands. This is also the reason why, when closing multiple instances of bash (eg. terminal sessions), only the commands from the last closed session can be found again.
To completely clear, you'll have to remove .bash_history without running bash.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
how do I clear passwd history of a user without compromising the audit trail for security?
in a nutshell, user abc wants to re-use his passwd ( he is not savvy with computers ) (4 Replies)
Discussion started by: A Stewart
4 Replies
2. UNIX for Dummies Questions & Answers
Hi...
i have one doubt pls...
1)can we clear the command line history in UNIX for a paricular login(scadm/root)if so how?.
2) can we see the time at which command executed.
history is showing like :
100 display
101 lock
102 exit (7 Replies)
Discussion started by: gincemathew
7 Replies
3. Solaris
hi
Any one can help me. I am using Sun_Solaris. The command history set to 100 at .cshrc. I am unable to clear the command histoy. In Linux it is very easy by giving command
history -c
I could not find any such type command to clear the history.
Is there any such type of command for solaris.... (3 Replies)
Discussion started by: prabir
3 Replies
4. Linux
Hi All,
Is there a way to check command executed by users in Linux for a specific date? I know we can use history, but it doesn't shows yesterday's executed commands.
rgds, (3 Replies)
Discussion started by: ronny_nch
3 Replies
5. Shell Programming and Scripting
Hi,
I would normally clear off the history entries from a terminal by using the following commands:
> ~/.bash_history
history -c
But this will remove the entries of that particular session only. How to prune all the entries of all login sessions for a particular user in a system?
N.B:... (3 Replies)
Discussion started by: royalibrahim
3 Replies
6. Linux
Clear in Linux
#!/usr/bin/ksh
am using clear in the script, but it is not working,
it gives an error as follows,
'xterm': unknown terminal type.
please help out.:confused:
---------- Post updated at 01:19 PM ---------- Previous update was at 12:01 PM ----------
if
then
... (2 Replies)
Discussion started by: pradebban
2 Replies
7. Shell Programming and Scripting
I want to clear the history so that no one should be able to see what commands I gave in the AIX OS level. I tried using history -c , ~/.sh_history, but they aren't working :wall:
Please tell me the command in ksh which can clear all the previous history? (4 Replies)
Discussion started by: lg123
4 Replies
8. Shell Programming and Scripting
Hi
Am using ksh shell
I need to remove history of commands used..
I tried
# rm .vi_history
# touch .vi_history
# chmod 600 .vi_history
This didnt work.. I tried also
# rm .sh_history
# touch .sh_history
# chmod 600 .sh_history (5 Replies)
Discussion started by: Priya Amaresh
5 Replies
9. UNIX for Dummies Questions & Answers
As in the title, how to clear the history entries?
For eg: if i enter history, series of linux commands getting displayed from day 1. I need to clear those entries and want linux commands to be stored freshly.
Thanks in advance (6 Replies)
Discussion started by: karthick nath
6 Replies
10. Programming
Hello friends! i am writing a code in which i take inputs (numbers) from user and count the total number of positive, negative and zeros entered. I need to clear my standard input buffer before scanf() command. My compiler is completely ignoring the fflush(stdin) command. its not even showing any... (1 Reply)
Discussion started by: Abhishek_kumar
1 Replies
LEARN ABOUT DEBIAN
devel::repl::plugin::readlinehistory
Devel::REPL::Plugin::ReadLineHistory(3pm) User Contributed Perl Documentation Devel::REPL::Plugin::ReadLineHistory(3pm)
NAME
Devel::REPL::Plugin::ReadLineHistory - Integrate history with the facilities provided by Term::ReadLine
DESCRIPTION
This plugin enables loading and saving command line history from a file as well has history expansion of previous commands using the
!-syntax a la bash.
By default, history expansion is enabled with this plugin when using Term::ReadLine::Gnu. That means that "loose" '!' characters will be
treated as history events which may not be what you wish.
To avoid this, you need to quote the '!' with '':
my $var = "foo!";
or place the arguments in single quotes---but enable the "Term::ReadLine" attribute "history_quotes_inhibit_expansion":
$_REPL->term->Attribs->{history_quotes_inhibit_expansion} = 1;
my $var = 'foo!';
and to disable history expansion from GNU readline/history do
$_REPL->term->Attribs->{do_expand} = 0;
CONFLICTS
Note that Term::ReadLine::Perl does not support a history expansion method. In that case, you may wish to use the Devel::REPL History
plugin which provides similar functions. Work is underway to make use of either History or ReadLineHistory consistent for expansion with
either the Term::ReadLine::Gnu support or Term::ReadLine::Perl.
perl v5.14.2 2010-06-13 Devel::REPL::Plugin::ReadLineHistory(3pm)