05-28-2012
Command History - size, security and more informations
Hi!
I need to know how to increase the size of History, creating greater security in it, and view commands with details such as date and time;
Also need to know if they learn to write a 'history' command made via WinSCP;
Thank you!
---------- Post updated at 01:36 PM ---------- Previous update was at 11:18 AM ----------
Another question about history: How to view the history of all users?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Dear all,
I am using solaris 6 O.S. and root previlege.I want to know how to get history of commands given by diff. users logged into the server.
I know that history command gives the list of previous commands for that particular log in session. In the simillar manner can I get simillar history... (3 Replies)
Discussion started by: vikasdeshmukh
3 Replies
2. Shell Programming and Scripting
Hi,
I'm looking for a way to get the date of creation for a file. Is it possible ? I know that these informations are in the i-node but I don't know how to access them (if the 'find' command can do it with option -ctime, I have reasons to believe in it).
Thanks for helping me ! (1 Reply)
Discussion started by: mullmafr
1 Replies
3. Solaris
hi all,
in my server there are some specific application files which are spread through out the server... these are spread in folders..sub-folders..chid folders...
please help me, how can i find the total size of these specific files in the server... (3 Replies)
Discussion started by: abhinov
3 Replies
4. UNIX for Dummies Questions & Answers
How do I make the history command, in addition to the past commands, display the hard path to the place where i modified or did my past action?
thanks in advance (2 Replies)
Discussion started by: cleansing_flame
2 Replies
5. Programming
hi,
i would like to know how to programatically obtain informations about existing NICs (both configured and non-configured if possible) on *NIX?
i need to write simple *NIX C/C++ program that will have these informations. i have tried to search forums (and also google) with no luck. any help... (2 Replies)
Discussion started by: nikoladsp
2 Replies
6. Shell Programming and Scripting
Hello,
I'm running a bash script and I'd like to get more accurate a runtime information then now.
So far I've been using this method:
STARTM=`date -u "+%s"`
.........
*script function....
.........
STOPM=`date -u "+%s"`
RUNTIMEM=`expr $STOPM - $STARTM`
if (($RUNTIMEM>59)); then... (3 Replies)
Discussion started by: TehOne
3 Replies
7. 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
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. Shell Programming and Scripting
Hi
I am trying to increase the number of commands recorded in my .bash_history file.
I followed what is indicated and have add to my .bashrc
export HISTCONTROL=ignoreboth
export HISTSIZE=1000000
export HISTFILESIZE=1000000
export HISTIGNORE='ls'but the .bash_history only contains 690... (5 Replies)
Discussion started by: louisJ
5 Replies
10. Shell Programming and Scripting
I'm probably sure I need to use either awk or sed judging by research but I'm not sure what exact command I have to do to do following...:wall:
So this is my text file
CPU 1 2 3 4 5 6
RAM 2 3 4 5 6 7
HAR 3 4 5 6 7 8
--------------
my input:
Cur_CPU=10
Cur_RAM=11
Cur_HAR=13
Desired... (5 Replies)
Discussion started by: simonirang
5 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)