01-16-2007
Quote:
Originally Posted by jxh461
HISTFILE=$HOME/.sh_history.$$
It seems it's working they way it is becasue you have it configured that way. One per shell pid.
10 More Discussions You Might Find Interesting
1. Solaris
How to set passwd history feature in Solaris 8 to stop users from using their old passwords? (4 Replies)
Discussion started by: amoorti
4 Replies
2. Solaris
i got solaris 10 DVD and i install it on intel 64.
how do i set history to vi for command line? i can use backup space as well, it goes with "^H".
this won't work, export EDITOR=vi, it response with not an identifier.
thanks
itik (4 Replies)
Discussion started by: itik
4 Replies
3. Solaris
Hi Solaris guys,
I just have my solaris 10 setup on x86 old box...
How can i get history key?
eg.
Linux using up/down arrow key to call history command...
HPUX using Esc-k
How can i do the samething in Solaris?
Thanks in advanced!
Regards,
gary (3 Replies)
Discussion started by: timontt
3 Replies
4. UNIX for Dummies Questions & Answers
How do you look at the whole list of previous commands you have used in VI? I know you can use the up and down arrows, but I know there's a way to see the full list. (5 Replies)
Discussion started by: cokedude
5 Replies
5. UNIX for Advanced & Expert Users
Hello.
I'm trying to get a Solaris (SunOS 5.10) shutdown and boot history. Unfortunately the /var/adm/wtmpx file does not cover the period I want to trace. It's been reset. Therefore the command, "last" (or "last reboot") does not reach back far enough.
Additionally the /var/adm/messages*... (4 Replies)
Discussion started by: etlpkby
4 Replies
6. UNIX for Advanced & Expert Users
Anyone knows how to display timestamp in Solaris since "HISTIMEFORMAT" variable is not supported in ksh ? (2 Replies)
Discussion started by: linuxgeek
2 Replies
7. Solaris
Dears
Kindly am requested to collect the date histroy that the system was rebooted, so is there any log file or command that i can find the time that the system was rebooted?
thanks a lot for you kind support. (2 Replies)
Discussion started by: thehero
2 Replies
8. UNIX for Dummies Questions & Answers
Can anyone tell this:
If two users are logged into the same server from different locations. Is there a way to see the history command of the other user? I tried the history command, but it is showing me only the commands I used.
Thanks in advance for your help.
Iamnew2solaris (1 Reply)
Discussion started by: iamnew2solaris
1 Replies
9. Solaris
I need to bump up the memory allocated to an Oracle database running on Solaris 10. While I see there is currently plenty of free memory to spare, how do I view the history of free memory on Solaris over the last month? What is the exact command?
---------- Post updated at 02:55 PM ----------... (0 Replies)
Discussion started by: mimimiami
0 Replies
10. UNIX for Beginners Questions & Answers
why in solaris 10 I do not get history when I have the role as root?
computer.root > history
I get history:not found
I am in computer.root > echo $SHELL
/bin/sh
computer.root >
how can I see roots history in the sh shell?
but in other shells I can only see my... (6 Replies)
Discussion started by: goya
6 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)