02-14-2008
Quote:
Originally Posted by
dsravan
can i increase the size of the history file. only 10 latest commands are being stored. If everybody has there own history file then how come i am able to see what others are typing?
The size of the history file is not in lines but in characters.
Lets assume your average command is about 25 characters then a HISTSIZE of 250 would more or less store 10 commands.
In case you make the change in the .profile as mentioned before, the name of the history file you are using is related to the "tty" you are working on.
Since everybody has a different "tty" the commands of each person are stored in a different file and you cant see the commands of others.
However, when you log off, your "tty" is released. The next person who logs on could get the same "tty" assigned as you were using before. If this is the case then only that person will be able to see your command history.
Unless ofcourse you make sure your private history file is deleted when you log off.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
Could you tell me if it is possible to add pseudo terminal name to the bash history?
I need to see from which terminal the command was issues. I found a variable HISTTIMEFORMAT that helps me to identify the time but cannot find similar thing for the pts number.
thanks,
Pavel. (0 Replies)
Discussion started by: pn8830
0 Replies
2. 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
3. Shell Programming and Scripting
Hellooooooo ;)
Today I've created a script that does some things (not important).
And for fun I want that it kills the terminal from which I launch it. (too lazy to press Alt-F4 lol)
So I write
#!/bin/bash
kill $PPID
but it doesn't work ... while if in my xterm I launch another xterm... (8 Replies)
Discussion started by: xib.be
8 Replies
4. UNIX for Dummies Questions & Answers
Hello every body,
Kindly inform me How Do i find out the time I executed a command previously on UNIX Solaris??
To be more specific and more clear about what i want to know is that I want a command the enables me to know the history and which command i run at this history/time.
FYI I used... (5 Replies)
Discussion started by: ahmedamer12
5 Replies
5. Shell Programming and Scripting
Hi,
I am using putty client to connect to my remote Linux server box, and I am connecting through ssh. That system runs bash shell. So, if I use multiple putty terminal, how can I replicate those commands that I ran in other terminals to be available/shared in the current terminal window (i.e)... (1 Reply)
Discussion started by: royalibrahim
1 Replies
6. Shell Programming and Scripting
Hi,
I've a script which kills all process, but i need a script shell script(sh), where it'll kill process on that particular terminal. below is example
TY=`tty`
for P in $TY
do
`kill -9 $P 2>/dev/null`;
done
echo "test process killed"
break
... (3 Replies)
Discussion started by: asak
3 Replies
7. UNIX for Advanced & Expert Users
Hi all,
My need is :
1. To know who , when , which command used.
2. Local user should not delete this information.
I mean , with an example , i can say
i have a user user1
i need to give all the following permissions to user1, :
a. A specific directory other than his home... (3 Replies)
Discussion started by: linuxadmin
3 Replies
8. UNIX for Dummies Questions & Answers
Hi all,
My need is :
1. To know who , when , which command used.
2. Local user should not delete this information.
I mean , with an example , i can say
i have a user user1
i need to give all the following permissions to user1, :
a. A specific directory other than his home... (1 Reply)
Discussion started by: sriky86
1 Replies
9. Shell Programming and Scripting
Good afternoon
I need to KILL a process in a single command sentence, for example:
kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'`
That sentence Kills the process ID corresponding to the program CAL255.4ge.
However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies
10. Shell Programming and Scripting
Hello elite shell/bash specialists,
I have done plenty of STFW and some RTFM, but I cannot find a clear solution to my challenge
Goal:
My goal is to have a script(of any language, preferably shell/bash/anything that can run things on unix), which will kill specific unix terminal windows for... (0 Replies)
Discussion started by: kamil-mech
0 Replies
LEARN ABOUT OSX
tklib_history
history(n) Provides a history for Entry widgets history(n)
__________________________________________________________________________________________________________________________________________________
NAME
history - Provides a history for Entry widgets
SYNOPSIS
package require Tcl 8.4
package require Tk 8.4
package require history ?0.1?
::history::init pathName ?length?
::history::remove pathName
::history::add pathName text
::history::get pathName
::history::clear pathName
::history::configure pathName option ?value?
bell
_________________________________________________________________
DESCRIPTION
This package provides a convenient history mechanism for Entry widgets. The history may be accessed with the up and down arrow keys.
::history::init pathName ?length?
Arranges to remember the history of the named Entry widget. An optional length determines the number of history entries to keep.
This may be changed later with ::history::configure. History entries must be added with the ::history::add command before they can
be seen.
::history::remove pathName
Forgets all history entries for the Entry pathName and removes the history bindings.
::history::add pathName text
This command is used to add history entries to an Entry that has previously had ::history::init called on it. This command should be
called from your Entry handler with the contents of the entry (or whatever you wish to add to the history).
::history::get pathName
This command returns a list containing the history entries for the Entry pathName
::history::clear pathName
This command clears the history list for the named Entry.
::history::configure pathName option ?value?
This command queries or sets configuration options. Currently the options recognized are length and alert. Setting the length deter-
mines the number of history entries to keep for the named Entry. Alert specifies the command to run when the user reaches the end of
the history, it defaults to
bell
entry .e
bind .e <Return> [list ProcessEntry %W]
::history::init .e
pack .e
proc ProcessEntry {w} {
set text [$w get]
if {$text == ""} { return }
::history::add $w $text
puts $text
$w delete 0 end
}
KEYWORDS
entry, history
history 0.1 history(n)