thank you guys for your replies. i already had a different history file for each ip address that a specific user is logged in the system. i did that similar with what ibmtech posted. but the problem is that when i connect with this user and run the
command i only see the history of my history file (with my ip address). so i guess the only way is what CarloM suggested. i must change the HISTFILE attribute of my environment and set it to the history file that i want to examine and then run the command
to see the history. thank you both
Hi,
I can use history command in unix to view my last 50 commands. But how can I run the previous commands easily? Can history command help?
Firebird (2 Replies)
Hi
We are sharing our envoirnment with our component teams. the plateform is SunOS 5.8 Generic_117350-41 sun4u sparc SUNW,Sun-Fire-V490.
All team logs in the domain with same user and perform activities.
Now for the system auditing purpose can somebody guide me how can I get the details when... (6 Replies)
Hello every body,
Kindly inform me How Do i find out the time I executed a command previously on UNIX Solaris??
To be more specific and more clear about what i want to know is that I want a command the enables me to know the history and which command i run at this history/time.
FYI I used... (5 Replies)
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)
Is it possible to find out the history of recently typed in commands of a particular user in a multi user system?
the history command expects a numeric argument with it. is it possible to find out the history o commands of a particular user say John_smith for example? (2 Replies)
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)
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
LEARN ABOUT DEBIAN
condor_convert_history
condor_convert_history(1) General Commands Manual condor_convert_history(1)Name
condor_convert_history Convert - the history file to the new format
Synopsis
condor_convert_history[-help]
condor_convert_historyhistory-file1[history-file2...]
Description
As of Condor version 6.7.19, the Condor history file has a new format to allow fast searches backwards through the file. Not all queries
can take advantage of the speed increase, but the ones that can are significantly faster.
Entries placed in the history file after upgrade to Condor 6.7.19 will automatically be saved in the new format. The new format adds infor-
mation to the string which distinguishes and separates job entries. In order to search within this new format, no changes are necessary.
However, to be able to search the entire history, the history file must be converted to the updated format. condor_convert_historydoes
this.
Turn the condor_schedddaemon off while converting history files. Turn it back on after conversion is completed.
Arguments to condor_convert_historyare the history files to convert. The history file is normally in the Condor spool directory; it is
named history . Since the history file is rotated, there may be multiple history files, and all of them should be converted. On Unix plat-
form variants, the easiest way to do this is:
cd `condor_config_val SPOOL`
condor_convert_history history*
condor_convert_historymakes a back up of each original history files in case of a problem. The names of these back up files are listed;
names are formed by appending the suffix .oldver to the original file name. Move these back up files to a directory other than the spool
directory. If kept in the spool directory, condor_historywill find the back ups, and will appear to have duplicate jobs.
Exit Status
condor_convert_historywill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
Author
Condor Team, University of Wisconsin-Madison
Copyright
Copyright (C) 1990-2012 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved.
Licensed under the Apache License, Version 2.0.
See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu
September 2012 condor_convert_history(1)