Sponsored Content
Operating Systems Linux History of executed command in Linux Post 302378485 by vidyadhar85 on Tuesday 8th of December 2009 02:56:51 AM
Old 12-08-2009
as far as i know there is no way to find commands date wise unless you made any arrangements i mean script on every time you log on and save it date wise every time you log off..
 

10 More Discussions You Might Find Interesting

1. Cybersecurity

Help Required: Command to find IP address and command executed of a user

Hi, I am trying to write a script which would figure out who has run which command and their IP. As i dont have any clue as to which commands would do this job, i request some gurus to help me on this. Thanks Vishwas (2 Replies)
Discussion started by: loggedout
2 Replies

2. Solaris

Can history commands show what time command executed

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

Need help! command working ok when executed in command line, but fails when run inside a script!

Hi everyone, when executing this command in unix: echo "WM7 Fatal Alerts:", $(cat query1.txt) > a.csvIt works fine, but running this command in a shell script gives an error saying that there's a syntax error. here is content of my script: tdbsrvr$ vi hc.sh "hc.sh" 22 lines, 509... (4 Replies)
Discussion started by: 4dirk1
4 Replies

4. Shell Programming and Scripting

System Command dies even when command gets executed successfully

Hi I have created a perl script & running it using Linux machine. I want my script to die when system command is unsuccessful but script is dying even when system command gets executed successfully. :wall: I am using the command below :- system($cmd) || die "FAILED $!"; print "Hello"; ... (2 Replies)
Discussion started by: Priyanka Gupta
2 Replies

5. UNIX for Dummies Questions & Answers

The history command: See other users command history

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

6. UNIX for Dummies Questions & Answers

Clearing history of commands executed

Hi, I have cleared the commands by using >$HOME/.sh_history. But if i issue HISTORY it shows some reference numbers but not the commands executed. But i want to truncate those line numbers too. May i know how i can achieve this? Thanks (1 Reply)
Discussion started by: pandeesh
1 Replies

7. Shell Programming and Scripting

Command is executed twice

Hi I try to run a command using bash script. The script should now look like this: #!/bin/bash case "$1" in start) sudo su - cispmgm -c "/usr/local/jdk/bin/java -Dworking.dir=/opt/ibm/cisp -Denvironment.target= -Xms512M -Xmx1024M -classpath... (1 Reply)
Discussion started by: nikolai.straess
1 Replies

8. UNIX for Dummies Questions & Answers

Want to get list of Linux commands used on specific date through HISTORY command

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

9. Shell Programming and Scripting

Need to echo command successful if command is executed successfully

Hello, I have written a command n shell script : srvctl relocate service -d t1 -s s1 -i i1 -t t1 -f If the above command executes successfully without error I need to echo "Service relocated successfully and If it errors out I need to trap the errors in a file and also need to make... (1 Reply)
Discussion started by: Vishal_dba
1 Replies

10. UNIX for Dummies Questions & Answers

Set Command to output a log of every command executed in the script

Hi Guys, I like to output every command executed in the script to a file. I have tried set -x which does the same. But it is not giving the logs of the child script which is being called from my script. Is there any parameters in the Set command or someother way where i can see the log... (2 Replies)
Discussion started by: mac4rfree
2 Replies
samlog_viewer(1)					      General Commands Manual						  samlog_viewer(1)

NAME
samlog_viewer - a tool for viewing and saving the SAM logfile SYNOPSIS
mmddhhmm[[cc]yy]] mmddhhmm[[cc]yy]] user] ofile] [file] DESCRIPTION
The command enables the viewing of part or all of the SAM logfile (or another file containing data in the same format) at varying levels of detail. This tool is run by SAM whenever the option is chosen. It can also be run independently of SAM, in either interactive or nonin- teractive mode. The command executes in either interactive or noninteractive mode, depending on the options given. In noninteractive mode, filters the source file and writes the resulting data either to stdout or to a destination file. In interactive mode, displays a graphical user inter- face enabling you to try different combinations of filtering, save one or more versions of the source file to other files, scroll back and forth among the logfile entries, etc. Under no circumstances is destructive to the contents of the SAM logfile (or whatever source file is specified by file). The contents of the source file are filtered and displayed (or output) according to the settings of the available filters. Multiple instances of can be run simultaneously without harmful effects. Filters supports three types of filters: level of detail, date/time, and user filters. These filters can be used in combination to provide highly selective logfile viewing. The level of detail filters control how much detail is displayed. The SAM logfile may contain entries of many different types. The entry types currently supported are: summary, detail, verbose, error, and note. The level of detail filters display some or all of these entry types, depending on which filter is chosen. The level of detail filters are: Displays only the higher level messages. These include summary, error, and note (warnings, other entries worthy of special attention) entry types. Includes level of detail, and adds detail log entries. If no level of detail is specified, this is the default. Includes level of detail, and adds verbose log entries. Displays only the literal commands that were executed. These commands may include HP-UX commands as well as SAM commands and scripts. The date/time filters are used to ask for entries written since a specific date/time, before a specific date/time, or both. The user filters are for viewing only those entries written by a particular user. If invoked with the option, its argument is used as the user whose entries should be shown. If user filtering is selected by the option, displays only entries made by that user and disallows any changes to the user filtering. This is useful for allowing nonprivileged users to run and see only those entries that pertain to them. Otherwise, allows the user filtering to be changed, or completely disabled, from its interactive filtering screen. Options The following options enable you to set up filtering and other attributes. If runs interactively, these attributes may also be set and modified in the various supported menus and displays. The available options are: The option sets the start date/time filter to the date/time given by its argument. The date/time is specified in the same way as it is for the command (see date(1)): mm Month specified as a two digit number (e.g., dd Day specified as a two digit number. hh Hour specified as a two digit number (24-hour clock form). mm Minute specified as a two digit number. cc Century minus one. cc is optional when specifying the year. yy The last two digits of the desired year. If this is not specified, the current year is used. To specify a year in two digits, the valid ranges are 70-99 (20th century) and 00-37 (21st century). To specify a year in four digits, the valid range is 1970-2037. If no start time is given, the beginning of the log is used as the start time. The option sets the end date/time filter to the date/time given by its argument. The date and time is speci- fied as described above for the option. If no end time is given, then an end date/time of infinity (no end time) is used. The option sets the desired level of detail. One of the letters must be specified as the required argument. The level of detail is set as follows: If the option is not specified, the level of detail is used by default. The option sets the user filter to the user name or user ID specified by user. Only entries logged by this user are displayed. If the option is omitted, entries logged by all users are displayed by default. The option causes the filtered output to be written to the output file ofile. The option implies the option described below. If ofile is the output is written to stdout. If is omitted, the output is written to either stdout (if is specified) or to the interactive display (if is omitted). The option enables automatic timestamping. If specified, each log entry is tagged with the time of day at which it was written. Timestamping is disabled by default. The option forces noninteractive behavior. If specified, runs noninteractively, using the default or specified values for all supported options and source/destination files. file Specifies the name of the file from which log data is read. The format of the data in the specified file must be the same as that used for raw SAM logfile data. If omitted, the SAM logfile is read. If file is stdin is read and runs noninteractively. If given, file must be the last argument specified on the command line. EXAMPLES
Capture the current contents of the SAM logfile using default filtering, and put into the file The following example does the same thing: View only the commands executed by SAM on behalf of user between 8am June 5, 1994 and 10pm August 14, 1994, and view the data interac- tively: Noninteractively read data from stdin, timestamp it, and save the result in a file called Do the same as above, but instead have the data appear on stdout: or FILES
SAM logfile. Archived version of created when the logfile is automatically trimmed by SAM when its size becomes too large. Its contents are included in the log entries read by Temporary files used by SEE ALSO sam(1M). samlog_viewer(1)
All times are GMT -4. The time now is 09:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy