12-17-2007
How are you trying to run these commands? What shell are you using? Different shells have different methods of accessing history and different files where the history is stored.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
How do I write a korn shell that will rename file with the current date. What I want to do is, I have a file that is re-written every day. But instead, I want to keep a 14 day history of the file. So I want to write a script that will rename the current file with a date attached to the... (2 Replies)
Discussion started by: watson2000
2 Replies
2. Shell Programming and Scripting
I'm trying to write a history feature to a very simple UNIX shell that will list the last 10 commands used when control-c is pressed. A user can then run a previous command by typing r x, where x is the first letter of the command. I'm having quite a bit of trouble figuring out what I need to do, I... (2 Replies)
Discussion started by: -=Cn=-
2 Replies
3. Programming
hii to all
i am developing a simple unix shell in c i want to add history feature in that how could i do that plz help if there is any tutorial or website plz put it here
history feature should be like that in bash, when press up key show the previous command typed in console
plz be... (1 Reply)
Discussion started by: vipin_jss
1 Replies
4. Solaris
Guys,
can u tell me some way in which the commands i execute on solaris system doesnot gets logged. It should not appear in history file.. Is there any shell which provide such solution or can I turn off the logging, if yes then how...
Help will be appreciated
Thanks (2 Replies)
Discussion started by: harpreetrekhi
2 Replies
5. Shell Programming and Scripting
How do I determine what my default shell is? If I'm root, how do I determine what my user's default shell is?
I think I'm running bash by default.
How do I write a perl program that can inject history into the shell's history so it can be retrieved with the history | grep command?
I have... (3 Replies)
Discussion started by: siegfried
3 Replies
6. 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
7. Shell Programming and Scripting
I admit I am terrible with scripting, so when I was asked to store users' command history lines and zip them on monthly basis what I did was to create a file "user_history_Feb" with the following contents:
Part A
# more user_history_Feb
cp -p /var/log/user_history/*history... (6 Replies)
Discussion started by: hedkandi
6 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. UNIX for Dummies Questions & Answers
Hello All,
Many developers in our company use same application account to log in Linux Box for code development, how can i redirect my log in shell history to a different file to avoid history being shown to others or accidentally execute the same command which i or others executed?
Thank you. (4 Replies)
Discussion started by: Ariean
4 Replies
10. Shell Programming and Scripting
I'm exploring OpenBSD and want to stick to its default shell, which is ksh. My goal is for my regular user ("bruno") and root user to have a shared history file. However, it seems that when running as root, ksh refuses to write to a HISTFILE that is owned by non-root user. This illustrates the... (3 Replies)
Discussion started by: DevuanFan
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)