03-15-2006
Well if we type history command in UNIX prompt, it will display the command executed by user
I want to know that which script is executing.... when we execute history command????
How the UNIX is managing the history command????
Please i want know the in/out details of history command......
And I want to write my own history script ......give me a hint to do this????
Help me out from this confusion
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey all,
When you run the 'ls -la' command it'll show you the time and dates of all files/directories. Now what I am trying to do is create a script that will tell me what files haven't been used in over the past 1 month and what the time and date is that the files that haven't been accessed in... (2 Replies)
Discussion started by: merlin
2 Replies
2. Solaris
On Solaris 8 and 10 is there a way history command can show what time a particular command was executed.
Pls reply.
Thanks (2 Replies)
Discussion started by: Tirmazi
2 Replies
3. Shell Programming and Scripting
Hello all,
Part of a script I am writing needs to check for a certain date..
example
If it is saturday between 1pm and 2pm, kick off this script.../directory/script.sh
need some pointers as to what the best way to do this is. (3 Replies)
Discussion started by: jeffs42885
3 Replies
4. Shell Programming and Scripting
Hi All,
Can i get the history command with date, so that i can know which command run at what time???
need it on urjent basis
Thanks (6 Replies)
Discussion started by: aish11
6 Replies
5. Shell Programming and Scripting
hi
i want to find a command in history for specific date .
is it possible that i can view ?? (1 Reply)
Discussion started by: scriptor
1 Replies
6. UNIX for Dummies Questions & Answers
I want to get list of linux commands used on Jan 01 2014 with the help of HISTORY command or some other linux commands,.
Kindly help. (3 Replies)
Discussion started by: karthick nath
3 Replies
7. Shell Programming and Scripting
HTML Code
archive_history() { HISTORYOLD=${HISTFILE}.archive CURTIME=`date` CURTTY=`tty` IP=$(echo $SSH_CLIENT | awk '{print $1}') if ; then echo "#-${HOSTNAME}-- ${CURBASHDATE} - ${CURTIME} ($CURTTY) ${USER} ${IP}----" >> $HISTORYOLD history... (2 Replies)
Discussion started by: rehantayyab82
2 Replies
8. Shell Programming and Scripting
HTML Code:
archive_history() { HISTORYOLD=${HISTFILE}.archive CURTIME=`date` CURTTY=`tty` IP=$(echo $SSH_CLIENT | awk '{print $1}') if ; then echo "#-${HOSTNAME}-- ${CURBASHDATE} - ${CURTIME} ($CURTTY) ${USER} ${IP}----" >> $HISTORYOLD history... (0 Replies)
Discussion started by: rehantayyab82
0 Replies
9. Shell Programming and Scripting
the given time is:
12:13:00
how do i subtract a 10 minutes from any given time?
date '12:13:00' '-10 min'
also tried this:
date +12:13:00 '-10 min' (2 Replies)
Discussion started by: SkySmart
2 Replies
10. UNIX for Beginners Questions & Answers
hi unix expert
how can i see the history of command that i entered in past?
history (1 Reply)
Discussion started by: abdossamad2003
1 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)