08-22-2001
Check the man page for your shell. Usually you just need to set an environment variable. For example from my ksh man page:
Quote:
HISTFILE If this parameter is set when the shell is invoked, its value is the path name of the file that is used to store the command history. The default value is $HOME/.sh_history. If the user has appropriate privileges and no HISTFILE is given, then no history file is used (see Command Re-entry below).
HISTSIZE If this parameter is set when the shell is invoked, the number of previously entered commands accessible to this shell will be greater than or equal to this number. The default is 128.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi, .sh_history keeps a list of past commands that we entered. but it has a limit and where do we set this limit. thanks. (1 Reply)
Discussion started by: yls177
1 Replies
2. UNIX for Advanced & Expert Users
Hi Friends,
We are currently 5 people using same Unix login-id on different terminals, .sh_history file contains list of commands typed by all 5 peoples(commands history) with the below list :
$tail .sh_history
ls -ltr
pwd
cd ..
ls -ltr
clear
cd temp
more kk.lst
Now my question... (9 Replies)
Discussion started by: krishna
9 Replies
3. UNIX for Dummies Questions & Answers
All,
I had a request to delete filed under a directory that was 35 days old . And they asked me to scedule it in CRON . I have done that .
I have use find and delete with mtime to perfrom this task .
But my script is not deleting this .cshrc,.exrc,.login,.profile,.sh_history file... (1 Reply)
Discussion started by: arunkumar_mca
1 Replies
4. AIX
hi
what's the difference between .sh_history and sh_history for root user?
thanks
itik (1 Reply)
Discussion started by: itik
1 Replies
5. AIX
Hello Everyone:
Does anyone know how I will setup my account to put timestamp in my .sh_history? I do not hold the root account. I am using AIX 5 and ksh shell. I tried every solution I can find in the internet but nothing seems to work OR I am just applying those in the wrong way. Anyone knows... (4 Replies)
Discussion started by: Orbix
4 Replies
6. UNIX for Advanced & Expert Users
Hello,
I've a script that verifies users connections.
This is the check part
do
NEVER=$(finger $USER | grep -i Never)
if
then
NAME=$(finger $USER | grep -i "In real life" | sed -e 's/^.*life: //')
echo $USER $NAME >> never_logged #" "$NEVER
fi
done
that for a specific... (6 Replies)
Discussion started by: gogol_bordello
6 Replies
7. AIX
I reviewed a couple old post where shockneck posted the use of the EXTENDED_HISTORY=ON variable to place a timestamp in the .sh_history file when using ksh and using the fc -t command to read the .sh_history file.
The fc command reads my history file. As an admin I would like to be able to read... (5 Replies)
Discussion started by: juredd1
5 Replies
8. UNIX for Advanced & Expert Users
Hi,
I'm on a linux machine. But I see that sh_history is not updated since february 15. How is it possible ?
Thank you.
uname -a
Linux MYSERVER 2.6.18-194.11.3.el5PAE #1 SMP Mon Aug 23 15:57:10 EDT 2010 i686 i686 i386 GNU/Linux
ls -al
-rw------- 1 oracle dba 3644 fév 15 09:28... (10 Replies)
Discussion started by: big123456
10 Replies
9. AIX
Hi,
I can't get all the enties of AIX .sh_history in email. only first entry of the history is emailed after executing the below code.
mail -s "History `date +%d-%m-%Y`" myemail@xyz.com <$HOME/.sh_history
Can anyone help? (3 Replies)
Discussion started by: m_raheelahmed
3 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)